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
73 ~ // Safety: ...
74 + unsafe {
|
thread 'rustc' panicked at 'internal error: entered unreachable code: attempted to remap an already remapped filename', compiler/rustc_span/src/source_map.rs:1107:34
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: internal compiler error: unexpected panic
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.1.58 (891ca5f 2021-11-15)
query stack during panic:
#0 [analysis] running analysis passes on this crate
If I apply some // Safety: ... line to solve undocumented_unsafe_blocks lint, then cause another ICE panic
Checking leetcode-rust v0.1.1 (/home/w/repos/my_repos/leetcode-rust)
thread 'rustc' panicked at 'assertion failed: self.start_pos.to_u32() + total_extra_bytes <= bpos.to_u32()', compiler/rustc_span/src/lib.rs:1677:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: internal compiler error: unexpected panic
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.1.58 (891ca5f 2021-11-15)
The text was updated successfully, but these errors were encountered:
I am trying to find a minimal reproduce code, but when I copy some unsafe code from my leetcode-rust repo to a single file cargo project, then this ICE was not reproduce. So I think currenly the only way to reproduce this bug/ICE is to clone my leetcode-rust repo
step to reproduce
Meta
Rust version (
rustc -Vv
):If I apply some
// Safety: ...
line to solve undocumented_unsafe_blocks lint, then cause another ICE panicThe text was updated successfully, but these errors were encountered: