>
> Note the explicit use case I listed is that of an unlock() in a finally
> block that *requires spawning a new fiber* in order to execute the actual
> unlock() RPC call: this is explicitly in contrast with the RFC, which
> specifies that
> >*ATTENTION*: A programmer must *never* attempt to create a new fiber
> while handling a CancellationException, as this behavior may trigger an
> exception during *Graceful Shutdown* mode.
>
>
I think you are right. This restriction increases complexity without
providing significant benefits. I will remove this condition from the RFC
entirely and simply state that the programmer should handle such situations
carefully.
Thank you!