Without.boats continues to just operate on such a great level.<p>These blog posts are so nicely dual audience targeting: they build a specific narrow case for where to go, what to do, that targets the Rust language folks having these discussions on mailing lists. But they also inform & set context, to make the information generally accessible. Having not only the internal focus, but also an external focus feels like a superpower for your argumentation.<p>That ability to rise above the mailing list experts-only context & to host a broader stage feels so powerful to me. Most of us wont get a digest of whats going on on the mailing lists & in hallway chats in Rust world. But we'll see what wb argued, and think about it, and remember these options if something else does happen. Technical blogging is <i>so</i> excellent.
The title is a little underwhelming, but this is a very good discussion of potential designs around async streams/iterators in Rust. Definitely worth a read.
Many (most?) disagree with this line of thinking, but I believe the "Rust will never have a 2.0" style thought is what ultimately leads these multi-year pursuits of perfect (or at least good enough to last "essentially forever"). The Editions provider a certain release valve for some styles of breaking changes, but I don't believe it's quite enough ultimately over the entire lifespan of a language which will undoubtedly grow cruft that even Editions cannot remove.
boats added this small addendum post today: <a href="https://without.boats/blog/coroutines-async-and-iter/" rel="nofollow noreferrer">https://without.boats/blog/coroutines-async-and-iter/</a>
> This is a lead-in to a longer term vision of introducing a “pinned effect.”<p>Seems really weird, pinning is not an effect, if anything it suppresses an effect (move).<p>Edit: I guess i should have kept reading the next paragraph, where he touches on a `Move` trait.