The getter needs to be more at least as visible as the setter if that's what you're talking about.

No support for write-only properties? :kotlin: Literally unusable!

There's a popular issue about in on YouTrack I think. It's definitely frustrating when you come across one of the few cases that would actually benefit from it.

For sure, definitely super rare to run across one though

I'm one of the weird ones who prefers not having them. Setting a value without being able to retrieve it feels more like just calling a function than interacting with a property, so I prefer to use a

private var

with a function call to set it. I find it makes the intent clearer.