Prioritize issues that can speed up development
Open
Nobody has claimed this yet.
enhancement
Impact: Low
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
There are certain features that are not super important from an end-user perspective, but it could be very useful for a debugger developer and they should be given higher priority. Here is a list of them:
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 reviewing the four linked issues: #352, #311, #349, and #180. Compare their usefulness to debugger developers and implementation scope, then define a clear priority order or decision record for the listed work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100