-
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
revert const_type_id stabilization #77083
Conversation
This reverts commit e385661.
Accepted for beta backport (there's not really any point in landing this if we don't backport). |
r=me, but also fine with waiting for @eddyb |
@bors r=RalfJung p=1 I think we should get this landed and backported quickly. |
📌 Commit 9b2c8d8 has been approved by |
Thanks! Sorry I didn't see it earlier, but yeah it doesn't really need my review since it's just a backport. I guess we can have the discussion on whether/when to re-land the stabilization elsewhere (perhaps a tracking issue?). |
⌛ Testing commit 9b2c8d8 with merge 2eb3d29f7479ceef4dc61f4329c4d05c57b36f27... |
💥 Test timed out |
Your PR failed (pretty log, raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@bors retry |
I actually would really like to use type ids in const contexts for what (I hope) are non-nefarious purposes 😄 We never actually had a proper tracking issue for this before and this PR currently links to |
I've created a tracking issue: #77125 |
Based on #77083 (comment) @bors r=RalfJung p=1 |
📌 Commit 0e2db57 has been approved by |
☀️ Test successful - checks-actions, checks-azure |
So who's doing the backport, are you or should someone else prepare a PR? |
I will do a rollup after compiler meeting today, to catch anything else that gets approved. |
…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`
The `const_type_id` feature was planned to stabilize in Rust 1.47, but this was reverted in: rust-lang/rust#77083 This causes errors when building `log` with the `kv_unstable` feature on Rust 1.47 or later. This patch removes the use of this no-longer-stable feature in those Rust versions.
This reverts #72488, which is currently on beta and scheduled to stabilize in
1.47.0
, based on #75923 (comment)It turns out we might not be quite ready to stabilize
TypeId
in const contexts before having a chance to rework its internals. SinceTypeId
is a bit of an oddity we want to be careful about how those internals are currently being relied on while making changes. That will be easier to do without having to also consider compile-time contexts.r? @eddyb