Rikito Taniguchi

Thank you for reporting! I'll take a look :)

Until we fix the design of the types, I'll work on Scala3 compiler by - Add the proposed types to `scalameta.proto` in https://github.com/tanishiking/semanticdb-for-scala3 and generate Types (and copy them to...

Last week I and @tgodzik talked about we may use [Maps](https://developers.google.com/protocol-buffers/docs/proto3#maps) for representing case patterns of MatchType, but I realized > the key_type can be any integral or string type...

> for TypeLambdas shouldn't it translate to something like this: 👍 > do we need bound and scrutinee for MatchType? Is it not covered in the TypeSignature ? - Yeah,...

Thank you for the comments @smarter! I really understand your concerns, especially about duplication of effort. I guess your suggestion means replacing SemanticDB with Tasty (or enabling semanticdb to embed...

> But do these tools directly interact with the semanticdb format, or do they use scalameta APIs? If the latter, then the exact on-disk format shouldn't matter for them. Ah,...

I looked into this a bit, and I found that we have the following trees for `classOf[...]`. ```scala classOf[Int] Literal( value = Constant( value = TypeRef(pre = ThisType(sym = package...

I personally think this issue is not so highly prioritized because of the `Counter arguments` I wrote.

👍 to `ApplyUsingTree` ```scala message ApplyUsingTree { Tree function = 1; repeated Tree arguments = 2; } ``` --- Since scalameta parses the following code to the scalameta AST below....

@googlebot I signed it!