Skip to content
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

rust: Eschew Box<MaybeUninit<T>>::write #1106

Commits on Aug 22, 2024

  1. rust: Eschew Box<MaybeUninit<T>>::write

    T-libs-api has consensus for stabilizing some of `feature(new_uninit)`,
    but not for `Box<MaybeUninit<T>>::write`. The replacement is trivial, so
    let's just do that, and RfL can simply move off the feature after it is
    stabilized. That will happen immediately after this unblocks Rust CI,
    as the relevant FCP has completed:
    
    rust-lang/rust#63291 (comment)
    
    This is required in advance of the stabilization because any remaining
    unstable API will be carved up into subfeatures as a direct result of
    stabilizing the majority of it. This code doesn't know about those yet.
    It can't, as they haven't landed, as building this code blocks Rust's CI
    but the expected-to-be-stabilized API can't be stabilized as long as
    this code requires that feature.
    
    Signed-off-by: Jubilee Young <[email protected]>
    workingjubilee committed Aug 22, 2024
    Configuration menu
    Copy the full SHA
    205a718 View commit details
    Browse the repository at this point in the history