ConfigureAwait(this) shouldn't run the continuation if the owner is destroyed.

Love your library!

Say you have some code like this:

async void Start()
{
    await Await.Seconds(5).ConfigureAwait(this);
    transform.position = new Vector3(1, 2, 3);  // will crash if object was destroyed
}

Currently, if the GameObject or Component is destroyed, the continuation runs immediately, which would cause a crash. I think it would be more intuitive if the continuation were cancelled instead. This is probably what the user wants most of the time and is consistent with how coroutines work.

[muckSponge]

Yes, I’m unable to come up with a logical situation where someone would tie it to an owner that doesn’t await on it or at least have some dependencies with the awaiting object so probably no point complicating things with an exception or exception option.

I’ve resolved the potential managed memory leak in 5430f351c9a06377d61018a946dcbb24c55418b4.

[mikehofm]

So my instinct is that once an object is destroyed, you rarely want to continue with the continuation. Your code is probably going to use some member of the owning object and crash; if the code had no dependencies on that object, it probably wouldn’t be in the object to begin with (or at least, you wouldn’t have called ConfigureAwait(this)). Of course, it’s hard to predict what use cases people might have.

I think the static Exception variable is safe here, but I don’t know enough about async/await to be confident.

One unrelated thing I noticed: in ContinuationProcessor, you don’t clean up the completed IContinuations. This could prevent any references held by the IContinuation from being garbage collected. You could probably add Array.Clear(currentQueue, 0, count); at the end of Process().