quantification of "satisfied" definitions for concepts
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
We define "satisfied" for concepts (or eventually "models") using phrasing such as:
Let
a,b, andcbe lvalues of typeT.Blargh<T>is satisfied only if: [things involvinga,b, andc]
This makes it unclear whether satisfaction depends on the choice of a, b, and c, or whether it's defined independent of that choice. Better phrasing would be:
Blargh<T>is satisfied only if, for anya,b, andcthat are lvalues of typeT, [...]
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 issue text, then search the draft for definitions that use “satisfied” with locally introduced lvalues or similar placeholders. Check how those definitions express quantification and identify the affected wording. Done means the relevant definitions unambiguously state whether satisfaction applies to any such values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tex
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100