lisudoku / lisudoku/lisudoku_solver
Nicer solve path for arrow?
Open
Nobody has claimed this yet.
arrow
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
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 with the linked solver entry point and screenshot to determine what “nicer solve path” means for the arrow puzzle. The issue names no files or tests, so clarify the desired solving behavior and completion criteria with the maintainer before locating the relevant solver code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100