[basic.start.term]/1 "sequenced before" followed by "function"
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
[basic.start.term]/1 says
Constructed complete objects ([dcl.init]) with static storage duration are destroyed and functions registered with std::atexit are called as part of a call to std::exit ([support.start.term]). The call to std::exit is sequenced before the destructions and the registered functions.
Clearly "sequenced before registered functions" makes no sense. It shall be "sequenced before calls".
Also be careful to say calls caused by std::exit rather than arbitrary calls.
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 at [basic.start.term]/1 in the draft and compare its wording with the referenced [support.start.term] clause. Check the surrounding sentence for the scope of calls caused by std::exit; done when the terminology is grammatically meaningful and the wording clearly refers only to those calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, tex
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100