<@U0BAA9MD5>: you can abuse the fact that class li...
# reflect
u
@desseim: you can abuse the fact that class literals have slightly different semantics for classes and type parameters and write your own "javaClass" function which will seem type-safe but won't in fact be, for reasons @apatrida is trying to explain