libs-team
libs-team copied to clipboard
The home of the library team
# Proposal ## Problem statement A common pattern that comes up when writing iterative logic over sequences is to special-case the first or last iterations. There are some existing APIs...
# Proposal ## Problem statement People are often unsure about what the rules are for creating a ZST. See, for example, , where the person made an unsound function. (Thankfully...
# Proposal ## Problem statement Many data forms that can be parsed from a string representation do not need UTF-8. Here, `FromStr` is unnecessarily restrictive because a byte slice `&[u8]`...
# Proposal ## Problem statement There is [`wrapping_shr`](https://github.com/rust-lang/rust/blob/2560b80a08597e4192aa3ee5a4670e36a5e4a7dd/library/core/src/num/uint_macros.rs#L1439) and [`wrapping_shl`](https://github.com/rust-lang/rust/blob/2560b80a08597e4192aa3ee5a4670e36a5e4a7dd/library/core/src/num/uint_macros.rs#L1406) a well as [`overflowing_shr`](https://github.com/rust-lang/rust/blob/2560b80a08597e4192aa3ee5a4670e36a5e4a7dd/library/core/src/num/uint_macros.rs#L1891) and [`oveflowing_shl`](https://github.com/rust-lang/rust/blob/2560b80a08597e4192aa3ee5a4670e36a5e4a7dd/library/core/src/num/uint_macros.rs#L1866) but no `saturating_shl` and `saturating_shr`. So on the one hand, this is for completion...
# API Change Proposal ## Problem Statement Currently, there is no mechanism in the Rust standard library to create a child process on Windows that does not inherit handles from...
In a previous libs team meeting, we discussed MSRV policy for the libc crate, and we debated between an N-1 policy and a slightly more conservative policy such as N-3...
# Proposal ## Problem statement It would be great if this code compiled: ```rust fn main() { let mut s = String::new(); write!(s, "hello").unwrap(); } ``` Using `write!` to append...
# Proposal ## Problem statement Currently, the best way to convert a slice of known size to an array reference with the same size (without unnecessary bounds checks) is something...
It has been suggested many times that `UnwindSafe` and `RefUnwindSafe` are more often an annoyance than they are useful, and that it might be time to effectively disable/remove them. Doing...
# Proposal ## Problem statement Implement `From` for `Arguments` seems to be a reasonable thing to do this. ## Alternatives The only thing I think of is utilizing private API...