Quick question, why is this allowed: ``` class A(...

# announcements

[janvladimirmostert]

Quick question, why is this allowed:

class A(b: String){
    var b: String

    init{
        this.b = b
    }
}

but when you add a setter, the property needs to be initialized, otherwise it doesn't compile?

class A(b: String){

    var b: String  // <- b needs to be inialized, otherwise no compile
    set(value) {field = value}

    init{
        this.b = b
    }
}

[janvladimirmostert]

+ @ijp @ndv

[diesieben07]

Because the setter might not actually set the underlying field. So if you have a custom setter, you must provide an initial value, so that the field can never hold "no value" (i.e. null).

[diesieben07]

The field initializer does not use the setter, to be clear.

[janvladimirmostert]

but the init is actually setting the value, so doesn't that guarantee that it's initialized ?

[ndv]

init is using the setter

[ijp]

@janvladimirmostert init is calling the setter

[marstran]

Init calls the setter, which isn't guaranteed to set the value.

[janvladimirmostert]

fair enough

[ijp]

why is nullable scenario handled the same though?

[ijp]

class A(b: String){

    var b: String?  // <- b needs to be inialized, otherwise no compile
    set(value) {field = value}

    init{
        this.b = b
    }
}

[ijp]

in this case field can hold null value

[marstran]

Null is not the same as "no value"

[diesieben07]

Yes, but if you want that, you need to be explicit about it. Things in Kotlin don't happen unless you tell them to happen. If you want null in the field, you need to put it there.

[janvladimirmostert]

null != uninitialized

[ijp]

sure, I understand

[ijp]

thanks

[janvladimirmostert]

is it possible in this scenario to declare b as lateinit in some way ? Doesn't seem like it

[diesieben07]

No, lateinit does not allow custom setters.