Updated explicit backing fields proposal

Kotlin / KEEP

Kotlin Evolution and Enhancement Process

Apache License 2.0

3.3k stars 356 forks source link

Updated explicit backing fields proposal #289

Open elizarov opened 2 years ago

elizarov commented 2 years ago

See explicit-backing-fields.md for the full text.

Please discuss in issue #278.

shaun-wild commented 2 years ago

This is awesome, I think it would make more sense the invert the type definitions though, the internal property keeps the internal type definition, then the public API is set using the get syntax:

val names: MutableList<String>= mutableListOf()
  get(): List<String>

Thoughts?