-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use Rust stable #1568
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tracking issue for things that we need to be stable in Rust so we can stop using nightly.
Overall I think we should seek to avoid introducing any more nightly features.
result_option_inspect
rust-lang/rust#91345 - It seems from the discussion it will never be stable, and maybe we should use https://docs.rs/tap/latest/tap/impl const Trait for Ty
and~const
(tilde const) syntax rust-lang/rust#67792result_flattening
) rust-lang/rust#70142#![feature(io_error_uncategorized)]
couldn't find that we use that actually?#![feature(async_closure)]
(RFC 2394 / RFC 3668) rust-lang/rust#62290try_trait_v2
, A new design for the?
desugaring (RFC#3058) rust-lang/rust#84277ops::Residual
(featuretry_trait_v2_residual
) rust-lang/rust#91285#![feature(c_size_t)]
(std::os::raw::c_size_t
/std::os::raw::c_ssize_t
) rust-lang/rust#88345is_some_and
- stable! need to upgrade to 1.70The text was updated successfully, but these errors were encountered: