A modern programming language that makes developers happier.

kotlinlang

Doesn't `Metadata` note which primary constructor parameters are also properties?

No, this information is not stored in the metadata. And I think it shouldn't, because your program should likely work exactly the same way on both
```
class A(val x: String)
```
and
```
class A(x: String) {
    val x: String = x
}
```
Storing the "is primary constructor property" flag in the metadata is of course possible, but would lead to a way for annotation processors and others to use that flag in a way that would introduce a difference between the two above programs.

Related issue: <https://youtrack.jetbrains.com/issue/KT-8849>

Makes sense what you say.
My idea was that _by default_ JSON decoding automatically uses all primary constructor parameters as properties to decode and all of these parameters which are also properties for encoding. It indeed doesn't really matter if they're in the constructor or not.

But for now I'm decided on relying on `!Flag.PropertyAccessor.IS_NOT_DEFAULT(getterFlags)` to select which properties are encoded automatically by default.