Handle "concurrent" compilation jobs
lhl2617 opened this issue · comments
I deliberately made it so that there is only 1 max compilation job running, but eh--nothing stops us
- either killing the previous process and letting the newest one take over; or
- allowing concurrent compilation jobs to run
I'm in favour of the former to conserve computing power.
Decided to kill the previous process--much easier to manage.