Closed
Description
This is a tracking issue for the ACP rust-lang/libs-team#375 .
The feature gate for the issue is #![feature(anonymous_pipe)]
.
// std::pipe
fn pipe() -> io::Result<(PipeReader, PipeWriter)>;
struct PipeReader {...}
struct PipeWriter {...}
impl PipeReader {
fn try_clone(&self) -> io::Result<Self>;
}
impl PipeWriter {
fn try_clone(&self) -> io::Result<Self>;
}
impl Read for &PipeReader
impl Read for PipeReader
impl Debug for PipeReader
impl From<PipeReader> for Stdio
impl Write for &PipeWriter
impl Write for PipeWriter
impl Debug for PipeWriter
impl From<PipeWriter> for Stdio
// unix {
impl AsFd for PipeReader
impl AsRawFd for PipeReader
impl FromRawFd for PipeReader
impl IntoRawFd for PipeReader
impl From<PipeReader> for OwnedFd
impl From<OwnedFd> for PipeReader
impl AsFd for PipeWriter
impl AsRawFd for PipeWriter
impl FromRawFd for PipeWriter
impl IntoRawFd for PipeWriter
impl From<PipeWriter> for OwnedFd
impl From<OwnedFd> for PipeWriter
// }
// windows {
impl AsHandle for PipeReader
impl AsRawHandle for PipeReader
impl FromRawHandle for PipeReader
impl IntoRawHandle for PipeReader
impl From<PipeReader> for OwnedHandle
impl From<OwnedHandle> for PipeReader
impl AsHandle for PipeWriter
impl AsRawHandle for PipeWriter
impl FromRawHandle for PipeWriter
impl IntoRawHandle for PipeWriter
impl From<PipeWriter> for OwnedHandle
impl From<OwnedHandle> for PipeWriter
// }
Steps
- Implement the ACP Initial implementation of anonymous_pipe API #127153
- Enable
std::io::copy
specialisation Enablestd::io::copy
specialisation forstd::pipe::{PipeReader, PipeWriter}
#128303 - Adjust documentation Add documentation for anonymous pipe module #133986 (see instructions on rustc-dev-guide)
- Move pipe API into
std::io
Movestd::pipe::*
intostd::io
#135583 - Stabilization PR Stabilize
anonymous_pipe
#135822 (see instructions on rustc-dev-guide)
Implementation history
Metadata
Metadata
Assignees
Labels
Category: An issue tracking the progress of sth. like the implementation of an RFC`#![feature(anonymous_pipe)]`Relevant to the library API team, which will review and decide on the PR/issue.This issue / PR is in PFCP or FCP with a disposition to merge it.The final comment period is finished for this PR / Issue.