This is a tracking issue for the RFC "2930" (rust-lang/rfcs#2930).
The feature gate for the issue is #![feature(read_buf)].
This is now called BorrowedBuf rather than ReadBuf.
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
read_buf_vectored, ReadBufs).rustc_must_implement_one_of, which is a language-observable thing, and thus needs some amount of oversight/documentation about that as a prerequisite of stabilization.read_buf return the number of bytes read like read does or should the ReadBuf track it instead? Some operations, like checking for EOF, are a bit simpler if read_buf returns the value, but the confusion around what is and is not trustworthy is worrysome for unsafe code working with Read implementations.assume_init be named?&mut ReadBuf to prevent unexpected swapping of the caller-provided ReadBuf?BufWriter copy_to specialization with the unstable read_buf feature #93305gustav3d, zopsicle, soargon, dimo414, Yanhao and 7 moreBlubjoshtriplett, dignifiedquire, iago-lito, DianaNites, bhgomes and 2 morejoshtriplett, programmerjake, 197g, robjtede, taiki-e and 17 more
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4