Skip to content

regression: adding a def'n for node-id NodeId(597) and def kind AnonConst but a previous def'n exists #128901

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
BoxyUwU opened this issue Aug 9, 2024 · 3 comments
Assignees
Labels
P-critical Critical priority regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@BoxyUwU
Copy link
Member

BoxyUwU commented Aug 9, 2024

[INFO] [stderr] thread 'rustc' panicked at compiler/rustc_ast_lowering/src/lib.rs:503:9:
[INFO] [stderr] adding a def'n for node-id NodeId(597) and def kind AnonConst but a previous def'n exists: DefKey { parent: Some(DefIndex(57)), disambiguated_data: DisambiguatedDefPathData { data: AnonConst, disambiguator: 0 } }
[INFO] [stderr] stack backtrace:
[INFO] [stderr]    0:     0x7f847c87e3a5 - std::backtrace_rs::backtrace::libunwind::trace::hec2dc58314f3b5ff
[INFO] [stderr]                                at /rustc/08328a323ecd80b443a8fcc72c6b1071f48e233f/library/std/src/../../backtrace/src/backtrace/libunwind.rs:116:5
[INFO] [stderr]    1:     0x7f847c87e3a5 - std::backtrace_rs::backtrace::trace_unsynchronized::h331ee0b0169d7b05
[INFO] [stderr]                                at /rustc/08328a323ecd80b443a8fcc72c6b1071f48e233f/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5

duplicate of #128016

@BoxyUwU BoxyUwU added T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. regression-from-stable-to-beta Performance or correctness regression from stable to beta. P-critical Critical priority labels Aug 9, 2024
@rustbot rustbot added the needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. label Aug 9, 2024
@BoxyUwU BoxyUwU removed the needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. label Aug 9, 2024
@jieyouxu
Copy link
Member

cc #128760, included in #129033

@lqd lqd modified the milestone: 1.81.0 Aug 22, 2024
@lqd
Copy link
Member

lqd commented Aug 22, 2024

Meh, no need for the milestone, it's equally confusing: initially seen on 1.81, but reverted as mentioned above.

@apiraino
Copy link
Contributor

apiraino commented Sep 4, 2024

I'm going to close this since #129033 has been merged

@apiraino apiraino closed this as completed Sep 4, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
P-critical Critical priority regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

6 participants