Carefully maintain branch history.
Open
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 35
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
To improve prediction accuracy.
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
No file, test, or entry point is named. First determine where branch history and prediction are implemented in the Clash processor, then clarify the expected history behavior and prediction-accuracy criterion before making a change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100