isocpp / isocpp/CppCoreGuidelines
F.60 seems out of place
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 45.3k
- Forks
- 5.6k
- PR merge metrics
- No merged PRs in 30d
Description
Rules for functions go from F.21 to F.60 and then go back to F.22:
Is this intentional or is it a bug?
Contributor guide
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
Review the function-rule sequence around F.21, F.22, and F.60 in the C++ Core Guidelines and determine whether the ordering is intentional. Done means either correcting the numbering or documenting the reason for the sequence; the issue provides no file or test location.
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
- Mostly clear
- Newbie friendliness
- 35/100