polish go1.23 range-over-func UX
- Dominant language
- Go
- Stars
- 24.9k
- Forks
- 2.2k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 17
Description
Tested with the current master:
UX improvement candidates:
* Collapse/hide the range body closure (or give an option like DAP implementation's `HideSystemGoroutines` or config) - Related golang/go#66468
* Hide range closure related variables from the local variable set (e.g. `.closureptr`, `#state`, `~r0`)
Contributor guide
Research direction
Start by reproducing the reported behavior on current master with a Go 1.23 range-over-func example, using the screenshot as the reference. Inspect how the debugger presents the range body closure and its local variables. Done means the closure can be collapsed or hidden, and closure-related variables such as `.closureptr`, `#state`, and `~r0` no longer clutter locals, with any configuration behavior verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100