Internal stack frames are visible when debugging code that uses constructor tearoffs
Open
P2
- Dominant language
- Dart
- Stars
- 224
- Forks
- 94
- Avg merge
- 7h 14m
- Merged PRs (30d)
- 2
Description
Example:
Contributor guide
Research direction
The issue names no files, tests, or reproduction entry point beyond a screenshot. Start by reproducing the constructor-tearoff debugging case and trace where stack frames are filtered; done means internal frames no longer appear while useful application frames remain visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100