You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
error: internal compiler error: compiler/rustc_traits/src/normalize_erasing_regions.rs:43:32: could not fully normalize `<M as core::payload::identifiable::Identifiable>::Id`
thread 'rustc' panicked at 'Box<Any>', compiler/rustc_errors/src/lib.rs:958:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust-clippy/issues/new
note: Clippy version: clippy 0.0.212 (fde6927 2021-01-02)
query stack during panic:
#0 [normalize_generic_arg_after_erasing_regions] normalizing `<M as core::payload::identifiable::Identifiable>::Id`
#1 [analysis] running analysis passes on this crate
end of query stack
error: aborting due to previous error
This means the underlying cause is that, in zero_sized_map_values, Clippy indirectly calls normalize_erasing_regions; which triggers the panic because that cannot normalize <M as Identifiable>::Id there. This is an expected behaviour since its document states "This is appropriate to use only after type-check: it assumes that normalization will succeed, for example.".
Just wanted to flag that #6840 is an ICE in v1.50.0 related to normalize_generic_arg_after_erasing_regions that is not fixed by the PR linked to this issue.
Code
I'm not sure about the exact part of code, that leads to ICE.
To reproduce issue, run clippy with
unstable-options
https://github.com/ivan770/spartan/tree/fade05f7896c2ecd8413bf20273c4236a7faeb78
Meta
cargo clippy -V
: clippy 0.0.212 (fde6927 2021-01-02)rustc -Vv
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: