Tracking issues for unstable library features used by std
#94971
Labels
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
T-libs
Relevant to the library team, which will review and decide on the PR/issue.
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
std
uses a lot of unstable library features. Whilecore
will most likely always have to use language features, we can strive forstd
to eventually be free of both unstable language and unstable library features.Some of these we'll need to stabilize, but some others we might be able to simply remove with some small changes to the code.
(See also #94970 for the language features.)
These are the library features we currently use in
std
:is_empty
function toExactSizeIterator
#35428#![feature(maybe_uninit_slice)]
#63569#![feature(mixed_integer_ops)]
#87840NonNull<[T]>::slice_from_raw_parts
#71941try_reserve
: RFC 2116 fallible collection allocation #48043vec_into_raw_parts
#65816trait Error
to core:Duration::try_from_secs_{f32, f64}
#83400The text was updated successfully, but these errors were encountered: