Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Killing a destroyed node should not throw an error #215
This can be argued to be correct behaviour. The user is attempting to perform an operation on a synth node which no longer responds and it can be argued that the user should be informed of this.
Perhaps an exception is too heavy a notification. However, I think we should keep this for
I understand this argument, but throwing an exception will do more than inform the user. It will stop their code from running. This doesn't work well when synth's can free themselves.