Skip to content

Switch library to Rust 2021 #88638

Closed

Description

@m-ou-se

This is blocked on the beta/bootstrap compiler being updated to 1.56.

Activity

  1. added
    S-blockedStatus: Blocked on something else such as an RFC or other implementation work.
    T-libsRelevant to the library team, which will review and decide on the PR/issue.
    on Sep 4, 2021
  2. m-ou-se commented on Sep 8, 2021

    @m-ou-se
    MemberAuthor

    This is blocked on an issue with assert and debug_assert using the edition of libccore instead of the one who invoked it. (For assert only on Rust 2015 and 2018, for debug_assert on all editions.)

    https://rust-lang.zulipchat.com/#narrow/stream/268952-edition-2021/topic/libcore.202021.20bug/near/252504325

  3. camelid commented on Sep 18, 2021

    @camelid
    Member

    (Note that this is blocked on #88638 (comment). The bootstrap compiler is now 1.56, so that's not a blocker.)

  4. added 2 commits that reference this issue on Oct 7, 2021
  5. added a commit that references this issue on Oct 8, 2021
  6. rukai commented on Dec 17, 2021

    @rukai
    Contributor

    I tried setting core to 2021 and got this error:
    image
    Adding rustc_const_stable to panic_fmt resolved the issue but its strange that this issue didnt appear until the edition was set to 2021.

    Is this another blocker? Or are we supposed to just add a rustc_const_stable?

  7. m-ou-se commented on Dec 17, 2021

    @m-ou-se
    MemberAuthor

    strange that this issue didnt appear until the edition was set to 2021.

    That's expected. panic!("just a string") didn't use panic_fmt in Rust 2018, but does in Rust 2021. See https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html

  8. m-ou-se commented on Dec 17, 2021

    @m-ou-se
    MemberAuthor

    @rust-lang/wg-const-eval: Looks like the "const-stable functions can only call other const-stable functions" check doesn't play well with #[rustc_do_not_const_check].

  9. fee1-dead commented on Dec 17, 2021

    @fee1-dead
    Member

    @rustbot claim

  10. m-ou-se commented on Dec 17, 2021

    @m-ou-se
    MemberAuthor

    @fee1-dead what part are you claiming? The migration of core is blocked on the const check, and the migration of std is already in progress in #92030.

  11. fee1-dead commented on Dec 17, 2021

    @fee1-dead
    Member

    I will fix the const check. And since this is a tracking issue I will unclaim. Sorry for the confusion

  12. removed their assignment
    on Dec 17, 2021
  13. added 3 commits that reference this issue on Dec 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-edition-2021Area: The 2021 editionS-blockedStatus: Blocked on something else such as an RFC or other implementation work.T-libsRelevant to the library team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions