IntersectMBO / IntersectMBO/ouroboros-consensus
Consider splitting `BlockQuery` to avoid the footprint type argument
Open
UTxO-HD
- Dominant language
- Haskell
- Stars
- 67
- Forks
- 43
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 43
Description
As noted by Joris [here](https://github.com/IntersectMBO/ouroboros-consensus/pull/1267#discussion_r1851652618) we might be able to split the BlockQuery datatype into a sum type therefore avoiding the footprint complications.
Contributor guide
Research direction
Start by reading the BlockQuery datatype and the linked discussion in pull request #1267, especially the referenced review comment. Determine whether representing BlockQuery as a sum type removes the footprint type argument complications. Done means the design is agreed and the resulting refactor preserves the existing consensus behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- blockchain, distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100