Nice crate!

[madsmtm]

Hey Drew!

I've been looking into the async story in objc2 today (madsmtm/objc2#279), gonna open a few issues (and later on probably PRs) in this repo because I believe you've taken the right approach in splitting this out from blockr to be generally applicable, and this'll be a useful crate for me to recommend to objc2 async users in the future.

Feel free to say so if you don't intend for this crate to be used by the wider ecosystem / gain that kind of "publicity" (with the effort that entails), then I'll go a different approach.

(Btw, thanks for making the license in your objr repos more permissive).

[madsmtm]

Oh, just found out that oneshot exists, might end up using that instead, not yet sure.

[drewcrawford]

Hi mads, glad you found it useful so far.

I was unaware of oneshot as well. Taking a glance at it I think the key differences are:

• continue has first-class support for running code on cancel. I think oneshot needs a wrapper for this? Personally I think going batteries-included on this is the way to go.
• oneshot has first-class support for blocking reads. continue would need a wrapper to do this. Personally I think going batteries-sold-separately on this is the way to go
• panic vs error, more in Propagate panics cleanly #7
• There are some different choices which lead to differing performance. For example oneshot hand-rolls its atomic-waker like capability, which ought to be a bit better. But in doing so it over-clones wakers, which ought to be a bit worse.