leanprover / leanprover/reference-manual
Link from "extended field notation" to "generalized field notation"
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 129
- Forks
- 67
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
What question should the reference manual answer?
We have a section on generalized field notation, but it took me a while to find it, because I was searching for the term "extended field notation", which we also use, for example here in the source code: https://github.com/leanprover/lean4/blob/4786e082dca22873d14d2a5b9b7c8843380c6e78/src/Lean/Parser/Term.lean#L836.
It would be cool if putting "extended field notation" into the search box found https://lean-lang.org/doc/reference/latest/Terms/Function-Application/#generalized-field-notation.
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
Review the generalized field notation page in the reference manual and the linked Lean/Parser/Term.lean usage of “extended field notation.” Add the requested connection or search term, then verify that searching for “extended field notation” leads to the generalized field notation page.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100