A modern programming language that makes developers happier.

kotlinlang

Question for folks using this in production...how do you handle savedstate (for app resurrection) when you only want to save part of your state but your screen state includes large lists of items?
E.g. saving the paging offset of an infinite scroll list...
You can't just mark your entire state class as parcelable because that would include your item list.

that doesn't work that well...see <https://kotlinlang.slack.com/archives/CPM6UMD2P/p1634152387055600>

you can't put it on values in the data class constructor...and what I really want is the inverse of it like what MvRx/mavericks provides (@PersistState) to tag the fields that should be preserved in savedstate