rust-lang / rust-lang/rust-clippy
'rustc' panicked at 'Box<dyn Any>'. Error when making advent of code scripts
Open
Nobody has claimed this yet.
I-ICE
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
Rust Version : rustc 1.65.0 (897e37553 2022-11-02)
Clippy version: clippy 0.1.65 (897e3755 2022-11-02)
Github Tag
error: internal compiler error: src\tools\clippy\clippy_utils\src\consts.rs:134:22: Not an int type
thread 'rustc' panicked at 'Box<dyn Any>', /rustc/897e37553bba8b42751c67658967889d11ecd120\compiler\rustc_errors\src\lib.rs:1462:9
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.65 (897e3755 2022-11-02)
query stack during panic:
#0 [analysis] running analysis passes on this crate
end of query stack
When running cargo clippy in directory RustLangFun\advent_of_code_2022>, the error was thrown.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the panic by running cargo clippy in the RustLangFun/advent_of_code_2022 directory from the linked Clippy_Error release. Then inspect clippy_utils/src/consts.rs around line 134 and the reported analysis path. Done means the scripts no longer cause the internal compiler error or rustc panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100