track whether a non-coherence `TypingMode` has been used to reuse cache entries
Open
Nobody has claimed this yet.
C-feature-request
T-types
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
see the WIP branch https://github.com/lcnr/rust/tree/typing-mode-is-coherence.
It is now fairly straightforward to track whether evaluation relied on the exact typing mode. finishing this work should result in a reasonable perf improvement
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 reviewing the WIP branch typing-mode-is-coherence linked in the issue and trace how evaluation records the typing mode used for cache entries. Determine the remaining work needed to reuse entries when evaluation does not depend on exact coherence, then verify that the change produces the intended performance improvement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100