[expr.prim.req.nested] misuse of term "unevaluated operand"
Open
@jensmaurer is already working on this.
Since Aug 20, 2021.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
[expr.prim.req.nested]p2: "A local parameter shall only appear as an unevaluated operand (7.2) within the constraint-expression."
This allows requires (T a) { requires sizeof(a) == 4; } but does not allow requires (T a) { requires sizeof(f(a)) == 4; }, because the term "unevaluated operand" only applies to the immediate operand of various contexts. I believe the intent here is "An unqualified-id naming a local parameter shall not be potentially evaluated." or similar.
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.
Assessment
This issue has not been assessed yet.