-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
ICE: Expected module, found DefId #75982
Comments
Assigning |
This is because an integration I'll thus kindly ask for this to be "re-prioritized", if possible, thanks. @rustbot modify labels: +I-prioritize |
Assigning |
@rustbot ping cleanup This needs mcve and bisection |
Hey Cleanup Crew ICE-breakers! This bug has been identified as a good cc @AminArria @camelid @chrissimpkins @contrun @DutchGhost @elshize @ethanboxx @h-michael @HallerPatrick @hdhoang @hellow554 @imtsuki @JamesPatrickGill @kanru @KarlK90 @LeSeulArtichaut @MAdrianMattocks @matheus-consoli @mental32 @nmccarty @Noah-Kennedy @pard68 @PeytonT @pierreN @Redblueflame @RobbieClarken @RobertoSnap @robjtede @SarthakSingh31 @shekohex @sinato @smmalis37 @spastorino @Stupremee @tamuhey @turboladen @woshilapin @yerke |
searched nightlies: from nightly-2020-07-20 to nightly-2020-08-25 bisected with cargo-bisect-rustc v0.5.2 |
Minimized: // src/lib.rs
const _: () = {
#[path = "foo.rs"]
mod foo;
};
// src/foo.rs
#[macro_export]
macro_rules! my_macro {
() => {}
}
// src/main.rs
fn main() {
weird_path::my_macro!();
} |
…t, r=petrochenkov Compute proper module parent during resolution Fixes rust-lang#75982 The direct parent of a module may not be a module (e.g. `const _: () = { #[path = "foo.rs"] mod foo; };`). To find the parent of a module for purposes of resolution, we need to walk up the tree until we hit a module or a crate root.
Found in the
pr-75180
crater run:ICEs:
This ICE happens on:
rustc 1.47.0-beta.1 (0f91f5c28 2020-08-25)
rustc 1.47.0-nightly (2d8a3b918 2020-08-26)
but
rustc 1.45.2 (d3fb005a3 2020-07-31)
only shows a compiler error.The text was updated successfully, but these errors were encountered: