I've started developing some macros and recently I've hit a bug in my code which produced an infinite loop.
Once rust-analyzer starts running cargo the only way to stop it is to stop VSCode, this really hurts development, since VSCode now has the lock for the repo.
I should not need to stop the IDE to kill an external program from running, neither should I be expected to kill it with kill.
And even if I do kill it with kill, VSCode just restarts it...
A solution could be adding a button in the following dialog, which sends a SIGTERM signal to cargo?
I've started developing some macros and recently I've hit a bug in my code which produced an infinite loop.
Once rust-analyzer starts running cargo the only way to stop it is to stop VSCode, this really hurts development, since VSCode now has the lock for the repo.
I should not need to stop the IDE to kill an external program from running, neither should I be expected to kill it with
kill.And even if I do kill it with
kill, VSCode just restarts it...A solution could be adding a button in the following dialog, which sends a SIGTERM signal to cargo?
