If I have two `var`s with the exact same implement...

# announcements

[farmerbb]

If I have two `var`s with the exact same implementation in their setter functions, is it possible to extract that logic out into a single function then assign it as the setter?

[Ruckus]

Depends on the logic, but if it has a backing field, it will require at least some rewrite.

[farmerbb]

Yeah, I’m wanting it to include a backing field.

[Ruckus]

Depending on what you're trying to do, probably not, as there's no way that function could know which backing field you're talking about. If you restructure the of the new function to take in the current value and return the new you could.

[Ruckus]

Something like this maybe?

class Test {
    var a = "a"
        set(value) {
            field = checkValue(field, value)
        }
    var b = "b"
        set(value) {
            field = checkValue(field, value)
        }

    private fun checkValue(current: String, new: String): String {
        return if (new > current) new else current
    }
}

[farmerbb]

That makes sense. I was kinda hoping for something along the lines of set(value) = checkValue(field, value) but this seems clean enough. Thanks

[Ruckus]

Yeah, unfortunately the setter has to return Unit, so that won't work.

[streetsofboston]

What about writing a property delegate?

[streetsofboston]

class GreatestDelegate<T: Comparable<T>>(initialValue: T) {
    private var backingField: T = initialValue

    operator fun getValue(host: Any?, property: KProperty<*>): T  {
        return backingField
    }

    operator fun setValue(host: Any?, property: KProperty<*>, value: T) {
        if (value > backingField) {
            backingField = value
        }
    }
}

class Test {
    var a: String by GreatestDelegate("")
    var b: String by GreatestDelegate("_")
}

[Ruckus]

That is a far better idea. I'm ashamed it didn't even cross my mind.

[farmerbb]

Excellent, this is more or less the idea I was looking for. Appreciate it!