One problem there is that you usually want *two* backing fields (one for the mutable one, one caching the .asState version). The current design tries to be very clear about you getting just one field from your property.

🔍 Curious why we run surveys and interviews, and how your feedback shapes Kotlin?

Natalia Mishina, Paulina Sobieszuk, and Denis Ambatenne join to talk about how our user research works, how we use the results, and why your participation truly matters.

💬 Dec 11 | 3:00–7:00 pm CET | r/Kotlin

I still don’t understand why records came to be in such a restricted form

In fact, I think we should have even more of those hints in our language. Look at how cumbersome is to ensure stability in Compose, and the tooling around it. It would be great if we could say “I expect this to be stable”.

Given the importance of being tail recursive in the JVM, I think it makes sense to give a hint to the compiler to ensure it.

I know maintainers have no obligation to users, but I really dislike when authors push everybody to move towards their new idea, instead of leaving the old one to the community and keep both.