Saem Ghani

This has gone stale and the multiple statements via pipes is required first. It can be resurrected if and when needed.

This is now stake, please reopen when you start working on it again.

This is effectively done elsewhere and no longer necessary. If someone feels otherwise leave a comment.

Treesitter grammar is nascent and incomplete, not to mention incredibly memory intensive. I'm not familiar with the other person or work.

I can't replicate this with the latest nimsuggest. @StefanSalewski can you still replicate it?

> ... the best solution seems to me to extend the concepts spec; when it talks about how a proc must be "in scope", it can also suffice that instead...

> Don't think about the syntax Great, I'd rather stay at the conceptual level right now, because the thinking needs cleaning up. > think about the implications of a system...

For future reference, one can use the Microsoft provided C++ Debug extension to debug nimsuggest: Below is a snippet showing me launching nimsuggest against the vscode extension, feel free to...

This isn't actionable, at best I'm guessing you're using it with `weave`, also since there are number of these processes, you're probably using the vscode extension. It'll trigger suggestion requests...

Is the project simple enough to shrink down and meaningless enough to post as an example?