A modern programming language that makes developers happier.

kotlinlang

<@U4UGS5FC7> I wasn’t aware that that KEEP could help with that issue. But in the example I only see how a type class can replace the need for the `reified` keyword. In the end I still have a `KClass` instance and no information about the reified types’ generic arguments, do I?
Or is it hidden in the `Reified` instance itself?

It’s a very interesting discussion but also quite a big task to implement these changes. So it may make sense to handle the issues separately.

It’s also interesting to compare that KEEP to Swift as its protocol-conformance extensions are so simple yet powerful (and I love them).
It looks like in the KEEP the type classes’ methods are resolved at compile time while in Swift they’re resolved at runtime, aren’t they?

What confuses me a bit is that Swift has perfect symmetry (`Self` = Type, `self` = instance of `Self`) while the KEEP suggests two different words (`Self` and `this`) instead of (`This` and `this`). Don’t they relate to each other as in Swift?