-
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
Compiler crash in 1.76.0-beta.1 #119463
Comments
searched nightlies: from nightly-2023-11-11 to nightly-2023-12-28 bisected with cargo-bisect-rustc v0.6.7Host triple: x86_64-unknown-linux-gnu cargo bisect-rustc --start 1.75.0 --end 2023-12-28 --regress ice |
0x7f6adfe7f645 - core::panicking::panic_ |
That is line 18 to 33 |
WG-prioritization assigning priority (Zulip discussion). @rustbot label -I-prioritize +P-medium |
An interesting issue, @rustbot claim |
interesting that the crash also doesn't happen if we qualify the trait with |
The |
stop feed vis when cant access for trait item Fixes rust-lang#119463 It's not necessary to feed visibility when use a private trait. r? `@petrochenkov`
Rollup merge of rust-lang#119553 - bvanjoi:fix-119463, r=petrochenkov stop feed vis when cant access for trait item Fixes rust-lang#119463 It's not necessary to feed visibility when use a private trait. r? ``@petrochenkov``
right; i'm assuming it hits a different resolver codepath, despite both working the same if the referred ident is public. thanks for the quick fix! |
Code
A minimal example is slightly involved;the minimal triggering case seems tobe that a proc-macro produces code that attempts toimpl a trait that isn't visible from the location it ends up.edit: this turns out not to require macros at all.
Cargo.toml
src/lib.rs
src/main.rs
Meta
rustc --version --verbose
:This also occurs in nightly (
rustc 1.77.0-nightly (fb5ed726f 2023-12-28)
), but not in stable (which provides the correct complaint thatPrivateTrait
is not publicly re-exported)Error output
Backtrace
The text was updated successfully, but these errors were encountered: