Techatrix

Are you proposing that as an example, hovering over the `.` in a `.{}` should show its result location type similar to this:  I guess this...

Without some steps to reproduce this issue, a stack trace is probably not enough to clearly identify the issue. (and i think there are some entries in the stack trace...

I just took a look at coc.nvim. This is where inlay hint request appears to be constructed and send: [buffer.ts#L169-L188](https://github.com/neoclide/coc.nvim/blob/eba04ac7df3a24902a689ad5710cd156bdd963b8/src/handler/inlayHint/buffer.ts#L169-L188) The `range` parameter seems to come from a `visible_range` function...

> I disagree with using a compiler-rt function when there is a directly supported wasm operation. Maybe I am misunderstanding what is being meant by "directly supported wasm operation" but...

> Marking as "bug" and bumping priority because the status quo implementation deadlocks if the child process writes enough data to stdout and then tries to read from stdin. I...

The issue appears to unrelated to tagged unions: ```zig fn foo(comptime T: type, in: T) void {} ``` When hovering over `in`, it will show `type` as the type even...

Could you explain your issue in more detail?

Labels details have been reworked in #1746 and #1763. @ryuukk do they now display as you would expect?

no response so I am going to close this issue. AFAICR this has been fixed by #1763.

If this feature has no false-positives then it wouldn't hurt, right?