Sometimes we need to preserve generic types in run...

# language-proposals

[Egor Trutenko]

Sometimes we need to preserve generic types in runtime, for example if we want to be able to distinguish between Container<String> and Container<Int>.
A one particular solution (although not really flexible) would to subtype Container<T> with statically typed StringContainer : Container<String> and IntContainer : Container<Int>. The problem is, as aforementioned, it's not really flexible and we have to do it by hand.
What if we could somehow tell compiler that we want to generate such subclasses with statically saved type parameter for every class that uses original, generic class? E.g.

open class Container<sticky T> {
  ...
}
...
val sc = Container<String>()
if (sc is Container<Int>) { // unreachable }

Under the hood would turn into

val sc = StringContainer()
if (sc is Container) { ... }

Theoretically, it is possible to track down all the types which generic type is parameterized with in compile-time; To avoid some problems with subclassing this functionality could be restricted for non-final classes. Also there could be problems with multiple type parameters.
So, thoughts? Would this be useful, what more problems can this bring, is there ways to enhance it?

[Egor Trutenko]

Never seen it. Could you provide an example please?

[elizarov]

I think this called “reified” (not “sticky”) and is currently supported for inline functions only (but not supported for classes). The solution by @Ruckus is a way to go.

[Egor Trutenko]

I now realize I was referring to something like C++'s templates, so I don't think it's reifying. Also inline functions don't really help in defining what type parameter are we dealing with in collections, for instance, unless I'm missing something.