Use of value classes to wrap Kotlin primitives

[pnewell]

In reference to this point:

Skip does not wrap Kotlin’s primitive types. We have chosen the massive efficiency and interoperability wins that come with using Kotlin’s primitive types directly over the additional Swift language compatibility we might be able to achieve if we wrapped Kotlin’s primitives in our own classes.

Have you all considered using Kotlin inline value classes to wrap these? My understanding is that performance is largely the same as using the primitive itself.

This could unlock protocols for primitives and could also help strings in particular to act in a much more Swift-like way.

[marcprux]

We've discussed it in the past, and we're open to further discussion. The advantages you mention are enticing.