IssueTracker

I should probably elaborate on that a bit more here :P. The ideal case would be that data classes written in other modules work the same when consumed. A standard data class (no secondary constructors, `val` properties) works fine when in the same module. The errors produced are also pretty confusing. They'll usually give what they read from the bytecode (constructor params called "var0" or the like) and reports missing setters for fields without names of said fields.

I can confirm the bug and the workaround. The same problem arises when you use a data-class from a library with @Embedded

For the record - this was my problem: https://stackoverflow.com/questions/46581736/error-matching-constructors-when-embedding-from-library/46600403