A modern programming language that makes developers happier.

kotlinlang

and yes, I know I know, coercing values is very frowned-upon in Kotlin, but what if it is just coercing one type to another? As in, it is a one-to-one relationship, not a one-to-many. I believe that would be more sound, right? If `transparentlyCoerce` is tooooo crazy, then still `transparent value class` would fit well with Kotlin because it is opt-in, as in it can't be defined using extensions or anything else like that, and so it only works in the case of the value class explicitly declaring itself as being transparent.

All feedback is very welcome, and again I don't actually believe this will be considered as-is, but I feel like there's some merit to discussing this until we reach something that actually feels idiomatic for Kotlin