[lib] Make use of "introduce data races" consistent
Open
Nobody has claimed this yet.
lwg
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
LWG issues processing session:
Sometimes we refer to 20.5.5.9 [res.on.data.races], sometimes to 6.8.2 [intro.multithread].
Sometimes we say "conflict".
Sometimes we say "concurrent calls", sometimes we just say "calls".
We should harmonize that, possibly after consulting SG1.
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
Begin with the LWG issues processing session and review the references to 20.5.5.9 [res.on.data.races] and 6.8.2 [intro.multithread]. Compare uses of “conflict,” “concurrent calls,” and “calls,” then consult SG1 as suggested. Done means the affected standard wording uses consistent terminology.
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