[dcl.stc]/1 and [dcl.typedef]/1 each forbid "static typedef"
Open
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
The former states a subset of the restrictions of the latter (which also forbids things like constexpr typedef …), so it would be sufficient to drop "there can be no typedef specifier in the same decl-specifier-seq and".
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
Compare [dcl.stc]/1 with [dcl.typedef]/1 in the C++ standards draft. Review the quoted restriction and confirm that removing it leaves the broader prohibition in [dcl.typedef]/1 sufficient; done means the redundant wording is gone without changing the remaining rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100