Jacob Rothstein

Does `create-lockfiles` fix the problem with `cargo-edit` (`cargo add`)?

I just ran into this again — it should either be documented clearly that Race will never end even if the component streams do (both/either), or this should be fixed

The specific use case I had needed to terminate the stream when _either_ of the streams terminated, not both. It seems like there are valid use cases and intuitive explanations...

I came here to post exactly this, including the "I'm not sure if I should be relying on this being stable" but it broke my tests on CI but not...

I'm not sure if "wrap" in the description is the same as this, but I keep wanting it to be easier to delegate AsyncRead and/or AsyncWrite to an inner type,...

> After many reads of this sentence, I realized that you meant compatible with the futures crate, right? exactly that. futures/futures-util/futures-lite/async-std/smol all share a bunch of types that I was...

I'd add Async(Buf)?(Read|Write) traits to that list as absolutely essential for runtime-independent crates to be possible. I'm not sure that timers are all that much more important than io (network...

AsyncDrop would likely help with a lot of the pain of unexpected/external drops, I think. It's really awkward to work around the current inability to do async stuff in Drop...

I think a lot of people coming from js look for `Promise.all/Promise.allSettled/Bluebird.map(…, { concurrency: …})`. It took me quite a while to realize that I needed to make a `Vec`...

happy to take this on, although i'm not sure it's a bug in the semver sense (i think this is 0.x semver-minor in that it's a change in expected behavior...