RustDoc panics at 'no entry found for key' when documenting code that implements the acpi::AcpiHandler
trait
#104421
Labels
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.
When documenting code that depends on the
acpi
crate and contains a type which implements theAcpiHandler
trait fromacpi
, RustDoc panics with the message 'no entry found for key'.This panic appears to be quite similar to the one described in issue #103463. However, the commit fixing that issue was merged in #103649 (12 days ago), and this panic is still reproducible on the latest nightly (e631891 2022-11-13), while the panic with the
luminance
crate described by #103463 is not reproducible on the latest nightly. Additionally, unlike #103463, simplyuse
ingacpi::AcpiHandler
is not sufficient to cause the panic; the crate that depends onacpi
must actually implement the trait in order to cause RustDoc to panic. Therefore, I thought this seemed like it deserved a separate issue from #103463.Code
Cargo.toml
:lib.rs
A Git repository containing the reproduction is also available here: https://github.com/hawkw/rustdoc-panic-repro
Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: