A modern programming language that makes developers happier.

kotlinlang

No, because it's not true that values are transparently stored. Take a Kotlin Duration, for instance. We don't persist the Double value but instead adapt it to a database type. The same is true of your own value classes. Also multi-field value classes are in KEEP right now.

Sorry, I didn't mean in imply that they were.

After digging through some issues and PRs I found that `id INTEGER AS VALUE` is valid syntax to auto-generate a value class, so I was hoping that there were a few other nuggets of functionality that would allow me to get around the setup as-is.

Something like Room's database-wide column adapters, or some such. But it doesn't seem that way.

We do not do database-wide anything because you may want different storage representations depending on the table. The adapters are only defined once so it's not a big deal

Here's the keep for other people reading, got curious
<https://github.com/Kotlin/KEEP/pull/339|https://github.com/Kotlin/KEEP/pull/339>