Saying a `val` cannot be set outside of an initial...
# getting-started
w
Saying a
val
cannot be set outside of an initializer is like saying that non-null types cannot be null, which isn't necessarily true since
lateinit
lets you set the value later and just throws an error if accessed early. I get that it can't be done, but
lateinit
already lets you get out of the null limitation so it was more of a question of why the same can't be said for
val