jjl
jjl
It makes it easier to work with some of the futures composition primitives, which can get a bit hairy if you need to keep mutable refs about. You also correctly...
I've double checked and looks like I never introduced the change to require only `&self` to do a send/receive in any released copy (I've been working on a bit of...
When I merge #18 and release 1.0.0-rc0, this change is included. Please provide feedback on these changes as there are quite a few.
looks like you're right. i have a PR on this repo open for a rewrite that makes it usable more than once. i don't think that version suffers from the...
The PR turns it into a capacity one reusable channel. it pays some price for this relative to the platonic ideal of a oneshot channel, but i think there may...
oh, that's an interesting approach. and quite an interesting problem, heh.
Maybe. My local working copy I've been experimenting with some of this. The problem is that it makes it difficult to ensure safety (i.e. i have to expose quite a...
Actually, I should note that on my working copy, the arc is gone and replaced with a box because we already have atomic bitflags we can use.
yes, a box does cause heap allocation, however turning the arc into one moves us one step closer to an alloc-less api (because i would ultimately like to support no-std...
okay, i've pushed (most of) my local changes to the [feature/no-arc](https://github.com/irrustible/async-oneshot/tree/feature/no-arc/src) branch so you can have some idea of what i'm talking about. this is work in progress. but you...