The const-eval interpreter is called on incomplete/invalid/ill-formed code
Open
@oli-obk is already working on this.
Since May 23, 2024.
A-const-eval
C-bug
T-compiler
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
It looks like https://github.com/rust-lang/rust/issues/76064 is back. This is the source of countless ICEs. Just in the last few weeks:
- https://github.com/rust-lang/rust/issues/121858
- https://github.com/rust-lang/rust/issues/123690
- https://github.com/rust-lang/rust/issues/124436
- https://github.com/rust-lang/rust/issues/124164
As member of @rust-lang/wg-const-eval my position is that generally these are not const-eval bugs, but bugs in whatever part of the compiler is passing invalid data to const-eval. However, which part would that be? I am not sure whom to ping for this.^^
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.
Assessment
This issue has not been assessed yet.