Fixed an issue where a dependent task that hasn't started yet would retain itself forever unless it had a chance to start. That was happening because it was capturing itself while attaching to the finish event of the dependency. Meanwhile we want the task to retain itself after being asked to start after the other one, so that you can connect 2 things and let them go out of scope. Now it will still retain itself after being asked to start, even though it may not transition to Running state, but you can call cancel() to basically revert that request to start. If the task is falls out of scope at that point it will clean up.
Fixed an issue where a dependent task that hasn't started yet would retain itself forever unless it had a chance to start.
That was happening because it was capturing itself while attaching to the finish event of the dependency. Meanwhile we want the task to retain itself after being asked to start after the other one, so that you can connect 2 things and let them go out of scope. Now it will still retain itself after being asked to start, even though it may not transition to Running state, but you can call cancel() to basically revert that request to start. If the task is falls out of scope at that point it will clean up.

KieranHarper/Yakka,KieranHarper/Yakka