@elizarov Thanks for your thoughts. Yes, persistent data classes would be fantastic; I have struggled with building some way to do efficient immutable yet transformable data both in kotlin and in Java. Most of the time, I just bite the bullet and make copies of my data. This is fine for low-volume applications, but in a high-throughput scenario causes way too much garbage collection overhead.