It often happens that nim check, invoked by VSCode, hangs for whatever reason. This results in several hanging processes consuming lots of CPU (each fully occupies single core in my case):
I think it would make sense for VSCode not to invoke more than one nim check at a time, and kill previous process when invoking a new one.
It often happens that
nim check, invoked by VSCode, hangs for whatever reason. This results in several hanging processes consuming lots of CPU (each fully occupies single core in my case):I think it would make sense for VSCode not to invoke more than one
nim checkat a time, and kill previous process when invoking a new one.