runtimeverification / runtimeverification/haskell-backend
Booster Map matching deficiency
Open
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 224
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
During an analysis of a reported simplification issue in slack, the simplification log showed that booster was unable to match a singleton (key |-> value):Map with a pattern (K |-> _V) M:Map.
- Create a small example that demonstrates the issue
- Inspect the internalised terms for the subject and pattern
- improve matching code for internalised
KMapto be able to match this (usingM == .Map)
Contributor guide
No contributing guide indexed for this repository
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 creating the small example described in the issue and reproduce the singleton Map versus (K |-> _V) M:Map mismatch. Inspect the internalised subject and pattern terms and trace the internalised KMap matching path. Done means the matching code handles this case when M == .Map and the example no longer shows the deficiency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100