Tracking issue for `TypingMode` transition
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
#131856 transitions the type system from separately tracking the Reveal in the ParamEnv, and intercrate and defining_opaque_types in the InferCtxt to tracking all of that state in a shared enum TypingMode as a field on the InferCtxt.
This is a necessary step towards correctly handling opaque types after type inference, but during analysis. This needs a separate typing mode where we reveal the opaque types defined by that body without accidentally trying to define them. It may also be used to properly support negative reasoning in coherence.
This issue is mostly used to get something to point to in FIXMEs.
- for perf: modify const_eval queries to be named
_raw, take aParamEnvand have wrappers which assert that the typing_mode isPostAnalysis. - perrrf: intern
typing_mode
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
Start by reading #131856 and the TypingMode transition described here, then inspect the const-evaluation query entry points and InferCtxt state. The checklist mentions raw const-eval queries, ParamEnv, PostAnalysis, and interning typing_mode; completion depends on resolving those tracked design tasks and updating the related FIXME references.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100