-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Rename Iterator::get_unchecked #77201
Conversation
It's possible for method resolution to pick this method over a lower priority stable method, causing compilation errors. Since this method is permanently unstable, give it a name that is very unlikely to be used in user code.
@bors p=1 Waiting for CI to |
@bors r+ rollup=always |
📌 Commit 04a0b1d has been approved by |
💡 This pull request was already approved, no need to approve it again.
|
📌 Commit 04a0b1d has been approved by |
☀️ Test successful - checks-actions, checks-azure |
Backport of rust-lang#77201, manually done because of file renaming.
…ulacrum [beta] backports This backports the following: * revert const_type_id stabilization rust-lang#77083 * [mir-opt] Disable the `ConsideredEqual` logic in SimplifyBranchSame opt rust-lang#76837 * Rename Iterator::get_unchecked rust-lang#77201 (manually, because of file renaming and other issues on master causing literal cherry-pick to fail) * Rebase LLVM onto 11.0.0-rc3 rust-lang#77063 (bumping direct to master, see rust-lang#77063 (comment)). The last two have not yet been approved by compiler team, but I'm posting this now and going to go ahead and approve as I expect both to get approved and we want testing as much as possible before release in ~2 weeks. r? `@ghost`
#77308 backported this |
Closes #76479
r? @pnkfelix