Postponing defining val to init now gives warning (and in the future error). This seem to hamper clean code

1

The following code now gives the warning “Property must be initialized, be final, or be abstract. This warning will become an error in future releases”.

I really don’t think the proposed solutions give better code. How does the Kotlin developers envision this ideally should be done when I need to run initialize() before I can set id and textEntry?

class FooBar(
    idElements: List<Int>,
    defaultTextEntry: String? = null
) : IFooBar {
    override val id: DotIntID
    override val textEntry: DpTextEntry?

    init {
        val (id, textEntry) = initialize(idElements, defaultTextEntry)
        this.id = id
        this.textEntry = textEntry
    }
2

I can’t seem to recreate the error? Here’s what I tried (playground):

interface IFooBar {
    val id: DotIntID
    val textEntry: DpTextEntry?
}

class DotIntID
class DpTextEntry

class FooBar(
    idElements: List<Int>,
    defaultTextEntry: String? = null
) : IFooBar {
    override val id: DotIntID
    override val textEntry: DpTextEntry?

    init {
        val (id, textEntry) = initialize(idElements, defaultTextEntry)
        this.id = id
        this.textEntry = textEntry
    }
}


fun FooBar.initialize(idElements: List<Int>, defaultTextEntry: String?): Pair<DotIntID, DpTextEntry?> = TODO()
3

With IntelliJ IDEA 2023.2.3 where I put it into a huge code base:

must_be_initialized
must_be_initialized1063×644 49.8 KB

4

We have a very similar case.

Is this the same as https://youtrack.jetbrains.com/issue/KT-61228/False-positive-MUSTBEINITIALIZEDORFINALORABSTRACTWARNING-for-effectively-final-properties ?
If so, it looks like it’ll be fixed in 1.9.30.