Explore inlay hints for REPL results

[orestis]

What has Changed?

• I have added an InlayHintsProvider to try and show inline REPL results in a nicer way
• Unfortunately, it doesn't seem that this API is flexible enough for this
• Opening a PR just for archival purposes

[orestis]

Perhaps the inlay hints API could be useful for something else, but it seems to be very narrowly oriented towards type hints. I couldn't get the tooltip to show up, neither the command to execute, as both seem to be related to a position in the code that actually has a symbol.

[orestis]

I used this as a guide since the API is very sparsely documented.

[PEZ]

Thanks for providing this! Even if it turns out to be a dead end, it can save others from entering. 😄

The other use for this that I am thinking about, is to place a button after the current form and current top level form that evaluates the respective form. Maybe that's not possible either for the same reasons?

[orestis]

I couldn’t get the commands executed. Perhaps I used the wrong syntax though, not sure. To try things out just eval things and if the hints don’t show up immediately then scroll a bit or go to a different file and back again. (The lack of control for making hints show up is another factor against using this for interactive stuff)

[orestis]

An addendum: The hovers didn't show up because I have turned off hovers 🤦

It'd be interesting if someone with a more standard VScode setup could try this branch.

[PEZ]

Tried it now. I can reproduce the ”need to scroll to wake the hints up” problem.

However, I get the tooltips and I can execute the commands. (cmd-click)

We'll need to clear previous hints, but regardless I'd say this is success. 😄

[Cyrik]

This does look fun, I'll have a look as well.

The other use for this that I am thinking about, is to place a button after the current form and current top level form that evaluates the respective form. Maybe that's not possible either for the same reasons?

I've also been thinking about how to expose more eval commands as GUI elements so that they are easier to discover for beginners.
The other three options I thought about are CodeLenses, similar to pyhton:

Adding test arrows to top-level forms:

Add some of the eval commands to the "ctrl+." CodeActions provider (probably the ones that have more complex hotekyes, like "eval to tap>")

I like the CodeAction and CodeLense versions the best, but the inlay-hints screenshot does look interesting.

[riotrah]

Oh wow I'd love to implement all the above and make it configurable or something !!!

In general yes, more "vscode-native"-ish and GUI-integrated the commands are, the better imo