Lateinit primitive types

I am sure this has been asked before, why no lateinit primitive types?
However, I am just confused with the answer that lateinit primitives are technically impossible

From what I know the null value is used as uninitialized markers for object types underlyingly.
Why can’t we do the same with primitives using boxed primitives (Integer instead of int)?

We are able to do Int? but not lateinit var: Int
why?

1 Like

I think the fundamental reason for this not to work is that lateinit doesn’t change the type.

With this suggestion - which would work - then adding lateinit would change the type of the underlying object.

2 Likes

i mean adding the question mark to Int also changes its type from primitive to boxed primitive too, right?

1 Like

Yes, but that’s a direct change to the type, while lateinit is “further away” geographically from the type. I agree that it should just be allowed, but I can see why it isn’t a thing yet.
There is a bug for it on Youtrack: https://youtrack.jetbrains.com/issue/KT-15284

1 Like

Anyway, for now you can use Delegates.notNull() for a very similar effect:

var num by Delegates.notNull<Int>()

// println(num) // IllegalStateException
num = 8
println(num) // 8
1 Like