-
Notifications
You must be signed in to change notification settings - Fork 13.3k
rustdoc
causes a rustc
panic
#109733
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
Labels
A-resolve
Area: Name/path resolution done by `rustc_resolve` specifically
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
T-rustdoc
Relevant to the rustdoc team, which will review and decide on the PR/issue.
Comments
Can you post the panic you see on nightly? |
Details
|
Hm, |
Details
|
reduce: mod s {
pub use b::A;
pub trait A {}
}
use s::A;
/// [`A`]
pub fn f() -> () {} |
I think this ICE had fixed, maybe we can close this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-resolve
Area: Name/path resolution done by `rustc_resolve` specifically
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
T-rustdoc
Relevant to the rustdoc team, which will review and decide on the PR/issue.
Code
This happened when I ran
in
bevy/crates/bevy_ecs
, that can be found here: https://github.com/bevyengine/bevy/blob/aefe1f0739bb395d2454e05a1a812acab767892c/crates/bevy_ecs/src/lib.rsIn order to attempt to narrow it down, I ran
rustdoc
on every source file inbevy_ecs
.Only other file that caused the ICE is:
src/system/mod.rs
, which can be found here: https://github.com/bevyengine/bevy/blob/daa1b0209ae4c46cdda61b2263e2cfab88625937/crates/bevy_ecs/src/system/mod.rsMeta
rustc --version --verbose
:Note that this happens on
nightly
as well, but the location of the panic is different.Error output
Here's a backtrace with
RUST_BACKTRACE=full
.Backtrace
Recreate steps
The text was updated successfully, but these errors were encountered: