A modern programming language that makes developers happier.

kotlinlang

in kotlin is it more idiomatic to define a var* with a custom getter and setter for persisting a value or defining methods for both to be explicit about the persistence going on

<https://kotlinlang.org/docs/reference/coding-conventions.html#functions-vs-properties>

these aren't read only (you can change the value and hence cause persistence) so I don't know if those completely apply

What do you mean by persistence? Like to a database or file?

im in android land so im using shared preferences

Although it would kinda be idiomatic, persisting(calling `apply`) every `var` change wouldn't be ideal. You'll be better off with a DSL.

I'm assuming you have a class wrapping a `SharedPreferences` instance.

the setter of the `var` is calling apply. I don't have a class wrapping the shared preferences . what would you recommend that for? <@UBJF87EBY>

I thought you were writing a type safe wrapper for `SharedPreferences`. If you're not, then calling `apply` in `setter is fine.