15262ec6be
When working with an arbitrary reader or writer, code that uses vectored
operations may end up being slower than code that copies into a single
buffer when the underlying reader or writer doesn't actually support
vectored operations. These new methods allow you to ask the reader or
witer up front if vectored operations are efficiently supported.
Currently, you have to use some heuristics to guess by e.g. checking if
the read or write only accessed the first buffer. Hyper is one concrete
example of a library that has to do this dynamically:
0eaf304644/src/proto/h1/io.rs (L582-L594)
38 lines
863 B
Rust
38 lines
863 B
Rust
use crate::io::{self, IoSlice, IoSliceMut};
|
|
use crate::sys::Void;
|
|
|
|
pub struct AnonPipe(Void);
|
|
|
|
impl AnonPipe {
|
|
pub fn read(&self, _buf: &mut [u8]) -> io::Result<usize> {
|
|
match self.0 {}
|
|
}
|
|
|
|
pub fn read_vectored(&self, _bufs: &mut [IoSliceMut<'_>]) -> io::Result<usize> {
|
|
match self.0 {}
|
|
}
|
|
|
|
pub fn can_read_vectored(&self) -> bool {
|
|
match self.0 {}
|
|
}
|
|
|
|
pub fn write(&self, _buf: &[u8]) -> io::Result<usize> {
|
|
match self.0 {}
|
|
}
|
|
|
|
pub fn write_vectored(&self, _bufs: &[IoSlice<'_>]) -> io::Result<usize> {
|
|
match self.0 {}
|
|
}
|
|
|
|
pub fn can_write_vectored(&self) -> bool {
|
|
match self.0 {}
|
|
}
|
|
|
|
pub fn diverge(&self) -> ! {
|
|
match self.0 {}
|
|
}
|
|
}
|
|
|
|
pub fn read2(p1: AnonPipe, _v1: &mut Vec<u8>, _p2: AnonPipe, _v2: &mut Vec<u8>) -> io::Result<()> {
|
|
match p1.0 {}
|
|
}
|