When nodes are destroyed individually, all methods are converted to "nop" - functions that do nothing, so you can't perform operations that would fail without the properties and methods that have been cleaned up.
But calling destroy on the Seriously composition instance doesn't do this, so if, for example, you try to render a node after the composition has been destroyed, it may throw an error.
When nodes are destroyed individually, all methods are converted to "nop" - functions that do nothing, so you can't perform operations that would fail without the properties and methods that have been cleaned up.
But calling
destroyon theSeriouslycomposition instance doesn't do this, so if, for example, you try to render a node after the composition has been destroyed, it may throw an error.