A modern programming language that makes developers happier.

kotlinlang

The new `typeOf` intrinsic does not retain type annotations. Is this intended or a bug?

It is intended (thus far). However, it might be added in the future. Feel free to submit a feature request. What’s your use case for type annotations?

I don't have one specifically for `typeOf`, but it's another nail in the coffin for type annotations. They are not retained for Java reflection and even the previous workaround for `typeOf` (anonymous object in an inline function) does not retain them.

I just feel they never get the love they deserve

But what kind of love type annotations deserve? What would you be doing with them?

(I mean, I can come up with a few potential uses myself, but I’m interested in learning what would be the realistic use-cases in the context of `typeOf` operator)

Like I said, don't have anything for `typeOf` (yet?), but what I would love to be able to do is something like:
`val x: List&lt;@SomeValidation String&gt;`

If inline classes allowed some kind of `init` (or an internal constructor) that would solve that validation issue.
But in general it's sad that the annotations are supported in the language, but only half.

Can I sommehow retrieve the java type by typeOf?

I would love to use it with moshi:
```  @CheckReturnValue public &lt;T&gt; JsonAdapter&lt;T&gt; adapter(Type type) {
    return adapter(type, Util.NO_ANNOTATIONS);
  }```

Inline classes will cover the validation use-case and will support init for that. 

Inline classes don't allow initializer blocks.