[flat.map] `key_equiv` might be made an aggregate to simplify wording LWG3959
Open
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
But I'm not sure whether this has normative impact, because if copying Compare has some side effects, the difference would be observable.
This is now LWG3959.
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 by reviewing the [flat.map] wording referenced in the issue and the associated LWG3959 discussion. Determine whether making key_equiv an aggregate changes observable behavior when Compare is copied, then document the resolved normative wording and its impact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100