-
Notifications
You must be signed in to change notification settings - Fork 51
Stream trait and related issues #34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We were thinking of scheduling this for Aug 12 -- cc @withoutboats @nellshamrell @cramertj and @yoshuawuyts are y'all available on that date for the lang team design slot? (And others, those are folks who expressed interest to me in the past...) |
@nikomatsakis yes, that works for me! |
Works for me! |
Scheduled: calendar event |
Yes, I'll be there! |
Hmm, so I think we ought to postpone this by a week. In light of the Mozilla layoffs there is an important meeting that I have to attend that conflicts with this slot. |
I took the liberty of moving calendar invite to Aug 19. |
That cal event shows may 13th? Just to confirm this is aug 18 at 1p eastern time? |
Looks like this was bumped again to next week. |
Summary
In the context of the Async Foundations group, @nellshamrell has been drafting an RFC to stabilize the
Stream
trait. See e.g. rust-lang/wg-async#15 for the latest round of edits. While the actual content of the RFC is perhaps more libs than lang (introducing a trait), the choice of whether or not to introduce this trait touches on a number of lang issues, particularly around forwards compatibility, and I thought it would be good to discuss as a group.Some of the issues I thought particularly relevant:
Stream
trait with a futureLendingStream
(a.k.a., "streaming stream" or "attached stream") traitcc @rust-lang/wg-async-foundations @sfackler
Background reading
Draft RFC: rust-lang/wg-async#15
About this issue
This issue corresponds to a lang-team design meeting proposal. It corresponds
to a possible topic of discussion that may be scheduled for deeper discussion
during one of our design meetings.
The text was updated successfully, but these errors were encountered: