"schedule a yield continuation" was not taking into account that the current scheduling state can be null, in which case the priority source and abort source are null, and a non-abortable, user-visible continuation should be scheduled. The latter is handled already by the abort and priority source null checks, but these weren't being initialized to null if the inherited scheduling state is null.
"schedule a yield continuation" was not taking into account that the current scheduling state can be null, in which case the priority source and abort source are null, and a non-abortable, user-visible continuation should be scheduled. The latter is handled already by the abort and priority source null checks, but these weren't being initialized to null if the inherited scheduling state is null.
Fixes #106
Preview | Diff