Skip to content

Tracking Issue for core::stream::pending #91683

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

Open
3 tasks
ibraheemdev opened this issue Dec 9, 2021 · 1 comment
Open
3 tasks

Tracking Issue for core::stream::pending #91683

ibraheemdev opened this issue Dec 9, 2021 · 1 comment
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@ibraheemdev
Copy link
Member

ibraheemdev commented Dec 9, 2021

Feature gate: #![feature(stream_pending)]

This is a tracking issue for core::stream::{pending, Pending}, a stream that always returns Poll::Pending.

Public API

// core::stream

pub fn pending<T>() -> Pending<T> { ... }

pub struct Pending<T> { ... }

impl<T> Stream for Pending<T> { ... }

Steps / History

Unresolved Questions

  • None yet.
@ibraheemdev ibraheemdev added C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels Dec 9, 2021
@yoshuawuyts
Copy link
Member

yoshuawuyts commented Dec 14, 2021

Blocking concern: this function should not be stabilized before the working group has been able to complete a feasibility study of async overloading, as that may mean that we may no longer have an std::stream submodule. Instead we'd likely fold the functionality of std::stream into std::iter, exposing this as std::iter::pending instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

2 participants