`$@` (Variable properties) should be documented
Open
Nobody has claimed this yet.
- Dominant language
- Less
- Stars
- 680
- Forks
- 442
- PR merge metrics
- No merged PRs in 30d
Description
Under maps, section named: Using variable variables in lookups references lookups, not maps, so when I tried to apply it, the code looks like this
@foods: {
dessert: ice cream; // Turn into a map
};
@key-to-lookup: dessert;
.lunch {
treat: @foods[@@key-to-lookup];
}
Compilation result: variable @dessert not found. So if variable variables are not applicable to the new Maps, it should be removed from documentation.
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 locating the Maps section and the subsection titled “Using variable variables in lookups,” then compare its example with the reported compilation result. Done means the documentation accurately states whether variable variables apply to Maps, with the misleading material corrected or removed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100