`int` property on class not being carried over to Builder

[danielmunro]

hello, first of all, this is an awesome library, thank you for taking the time to write this. I have a class with a property int, which doesn't become part of the builder. Here's a snippet:

    val str: Int = 0,
    val int: Int = 0,
    val wis: Int = 0,
    val dex: Int = 0,
    val con: Int = 0,

the corresponding builder gets:

  private var str: Int? = null

  private var wis: Int? = null

  private var dex: Int? = null

  private var con: Int? = null

is this expected behavior? If not I'd be happy to help debug the issue. Thanks for reading and have a great day!

[YetAnotherMatt]

HI @danielmunro sorry for the late reply - GitHub doesn't seem to be notifying me of new issues :(
Admittedly I don't think that's a scenario I'd considered, but it's not the expected behaviour, no. I weill try to look into it.

[YetAnotherMatt]

Hi @danielmunro:
Debugging this issue, a field with the name int is not included in the list of members returned by core Javac code: com.sun.tools.javac.model.JavacElements.getAllMembers(TypeElement element) (which implements javax.lang.model.util.Elements), invoked here (line 111 of BuilderProcessor.kt:

    /** Returns all fields in this type that also appear as a constructor parameter. */
    private fun TypeElement.fieldsForBuilder(): List<VariableElement> {
        val allMembers = processingEnv.elementUtils.getAllMembers(this)
        ...
    }

So I'm afraid the short answer is "Javac won't let me include a field named 'int". I'll leave the issue open for anyone who has a suggestion for how to handle it (or better, a PR).

[danielmunro]

Hey @YetAnotherMatt thank you for taking a look, and for this great software! My "workaround" was to just use the full name, ie "intelligence", and that seems to work. I think this is better anyway. Feel free to close this issue if you want. Thanks again