Better Representation of Assignments (maybe Value Summaries)
- Dominant language
- Rust
- Stars
- 15
- Forks
- 0
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 15
Description
Right now we use ITEs, which are straightforward for sequential merges but become very annoying when we do parallel merges (we need to tear down the ITE into what I think are value summaries, and then reconstruct an ITE after moving concretes up front).
Find a better encoding, perhaps kevins idea of `Action::Assign(guard, value, dont_care_guard)` as a value summary
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how assignments are represented with ITEs and how sequential and parallel merges process them. Compare that flow with the proposed Action::Assign(guard, value, dont_care_guard) value-summary encoding; done means parallel merges no longer require tearing down and reconstructing ITEs.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100