I'm not even completely opposed to the suggestion,...

# language-proposals

[kirillrakhman]

I'm not even completely opposed to the suggestion, but having uninitialized nullable fields is a bit unidiomatic in Kotlin. the more kotlin-y way is to have primary constructor properties that you don't need to initialize yourself. of course you might have different use cases than me