Should the thing mentioned here be reported as a bug? <https://stackoverflow.com/questions/59822125/...

# announcements

[Kroppeb]

Should the thing mentioned here be reported as a bug?
https://stackoverflow.com/questions/59822125/kotlin-variable-initialization-for-child-class-behaves-weird-for-initializing-va

[Ivan Kubyshkin [JetBrains]]

This behavior is described in the documentation — https://kotlinlang.org/docs/reference/classes.html#derived-class-initialization-order

[Kroppeb]

I don't see where it's mentioned that the initialization of primitives is not executed if it's being set to their default value.

[Kroppeb]

Oh I see

If any of those properties are used in the base class initialization logic (either directly or indirectly, through another overridden open member implementation), it may lead to incorrect behavior or a runtime failure. When designing a base class, you should therefore avoid using open members in the constructors, property initializers, and init blocks.

[kqr]

I don't see it 🙂. this explains why it's printing 1 and then 33 but not the other case in my opinion. I would expect that in second case after x being initialized to 1, it would be "initiliazed" to 0 and not skipped. Although, yes it could be covered by it may lead to incorrect behavior or a runtime failure, but may should not imply should