Peter Munch-Ellingsen
Peter Munch-Ellingsen
> The sequence var x: T; unpack(y, x) does not compile under --experimental:strictDefs when unpack does not take an out parameter. Neither does the following snippet: > > ```nim >...
Removing the line which causes the exception makes Valgrind run clean, same for using a variable to store the result and explicitly returning it.
Just checked to see if this had been fixed in 2.0.4 and it is still present.
I designed this feature but never got around to implement it. Basically my idea was that you could define a preamble for certain file extensions. When nimlsp opens a file...
Hmm, seems like an issue with asynctools. Maybe try to bring it up there and see if they know whats wrong. When you do, please mention this issue so we...
I haven't quite decided yet if this should be added to the README. So let's keep it open for now
Hmm, this is likely a bug in nimsuggest. But could you try to update to the latest NimLSP version 0.4.6? I see that between your version 0.4.4 and the current...
Why would we need to sleep with synchronous IO? It should just block on the read of stdin. And why 16ms?
Ah right, I guess 16ms makes sense. But it still doesn't make sense that it busy loops in an infinite loop. Since its using synchronous IO it should be blocking...
Again, it doesn't make any sense that sleeping before a synchronous read should affect CPU performance short of just limiting the amount of actual work it's able to do.