Debugger info widget should offer to show expressions that cannot be evaluated properly
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Right now the debugger info widget only shows those expressions that can be evaluated and get a value from. This might be desirable in many cases, but we should also offer an option to list all relevant expressions even if some of them cannot be evaluated. Main motivation:
- People expect to see the expression there. If they do not see it, they get puzzled. If the expression is listed by with no value, then people understand it cannot be evaluated
- It would be easier for developers to see some expressions cannot be evaluated and try to figure out why
- Once https://github.com/Vector35/debugger/issues/635 is done, even if the value cannot be evaluated, people can see the storage of the expression (which should be available and accurate in almost all cases), and then understand why the expression cannot be evaluated
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 at the debugger info widget and trace how it selects expressions that evaluate successfully. Determine where an option to list unevaluable expressions belongs, then verify that relevant expressions appear without values while evaluable expressions retain their current display; issue 635 may provide storage information once completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, reverse-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100