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

# announcements

[diesieben07]

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

[elizarov]

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?

[diesieben07]

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.

[diesieben07]

I just feel they never get the love they deserve

[elizarov]

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

[elizarov]

(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)

[diesieben07]

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<@SomeValidation String>

[diesieben07]

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.

[Paul Woitaschek]

Can I sommehow retrieve the java type by typeOf?

[Paul Woitaschek]

I would love to use it with moshi:

@CheckReturnValue public <T> JsonAdapter<T> adapter(Type type) {
    return adapter(type, Util.NO_ANNOTATIONS);
  }

[jw]

It requires kotlin-reflect, sadly

[elizarov]

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

[diesieben07]

Inline classes don't allow initializer blocks.

[elizarov]

Yet.

[diesieben07]

oh. That's good to know! Thank you