A modern programming language that makes developers happier.

kotlinlang

Don't know about the exception, but wouldn't it be easier and safer to just make the field nullable?

sure :slightly_smiling_face:  I thought this trick was a bit better with "isInitialized" it makes the code's intention clear

I disagree: I think `lateinit` should be reserved for things like DI frameworks or Beans-type builders.

`::isInitialized` is for really exceptional situations.

I don't know, in my case, it's pretty much what lateinit is intended for. It's normally not null (except when it was not yet initialized).  I'd say this is not an unreasonable usecase for it.

I would agree with Karel, that you shouldn't use isInotialized in your case, it doesn't looks reasonable. Looks that your case is Android, so you should check lifecycle implementation of your component and use lateinit (it's actually good use case of lateinit for Android components because classes managed by the system and you cannot use constructor) or use nullable

Thanks for your input, but really that was not the point of my question :stuck_out_tongue:

independently of whether it's a good idea to do this, it should work (IMHO?)