increpare / increpare/PuzzleScript
optimisation idea: do some fancier movement collection where possible like you do with objects
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 185
- PR merge metrics
- No merged PRs in 30d
Description
[ moving player ] -> [ player ]
produces
(83) DOWN [ up player ] -> [ player ]
(83) DOWN [ down player ] -> [ player ]
(83) DOWN [ left player ] -> [ player ]
(83) DOWN [ right player ] -> [ player ]
(83) DOWN [ action player ] -> [ player ]
Why not allow "moving" to remain on the lhs if it's not needed on the right? (A: because it makes things complicated ^^ )
I mean, just to have
DOWN [ moving player ] -> [ player ]
in the compiled version
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 by locating the compiler path that expands movement rules and compare it with the existing object-collection optimization mentioned in the issue. Use the examples as the acceptance check: the compiled output should retain moving on the left-hand side where it is unnecessary on the right, without changing rule behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100