Sake target for debugging
Open
Nobody has claimed this yet.
testneeded
whateverable
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Mentioned in the commit message of this commit 025c05081acbf9548c0308613ab9f604535541d8.
Contributor guide
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 reading commit 025c05081acbf9548c0308613ab9f604535541d8, which the issue identifies as the source of this request. Locate the existing Sake targets and determine what debugging target is intended; done means the requested target is defined and its debugging behavior is verifiable.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100