Clarify how magic wand instances are matched with those in the current state
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by locating the tutorial section covering magic wand instances and read its surrounding explanations. Document the distinction between value matching for expressions independent of the current lhs/rhs heap and syntactic matching for dependent expressions, adding examples that make both cases clear.
Written by the indexing model from the issue text.
Description
Created by @alexanderjsummers on 2019-08-28 10:55
We should document this in the tutorial (though it is a little advanced): all expressions which don't depend on the "current" (lhs/rhs) heap are matched by value; those which do depend on the current heap are matched syntactically. We should add examples.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
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.
More from viperproject/tutorial
-
enhancement major
Difficulty 1/5 Under an hour Newbie friendliness 72/100
viperproject/tutorial#2 ·
All issues in viperproject/tutorial
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·