SirOlaf

Examples are not hard to come by, here is a contrived one ```nim import std/asyncdispatch proc test() {.async.} = raise newException(ValueError, "Async error") waitFor test() ``` The error will grow...

> The construction syntax I'm interested in to get comparable ergonomics of use with other languages (for `nim-result`): > > ```nim > let x: Either[int, string] = Le(42) > ```...

Looking into this issue, will open a PR soon

This seems to have some issues inferring exceptions of generic procs. ```nim proc foo[T](x: T) = discard foo(1) ``` A bell for the call foo(1) appears, supposedly raising "Exception". ~~I...

It propagates without issues in the sempass2 step of compiler, nimsuggest does not get the instance symbol and that is what fails. I tried hacking together a fix to demonstrate...

No need for anything special, result just doesn't receive a call to destroy here. This will eat up memory pretty quick ```nim proc leakMemory(): seq[char] = result = newSeq[char](128) raise...

Real issue seems to be that `typed` arguments lose info about generic params for some reason. Before that related fix, type checking would also lose the same info so it...

https://github.com/nim-lang/Nim/pull/23202#issuecomment-2000263308 Have you not run into this? It makes the feature borderline useless right now. Not something to spread everywhere.

Well as mentioned I don't know exactly how to go about fixing this, what I got working is displaying the correct symbol but that broke some highlighting according to tests...

Will try. For reference, this is what it currently looks like for the typehint upon hover. Might be desirable in a modified state that shows that the function is a...