isocpp / isocpp/CppCoreGuidelines
I.2: Avoid non-const global variables
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 45.3k
- Forks
- 5.6k
- PR merge metrics
- No merged PRs in 30d
Description
I.2 has the following:
"Alternative: If you use global (more generally namespace scope) data to avoid copying, consider passing the data as an object by reference to const. "
I marked part in bold italic. I suggest amending it to read:
"Alternative: If you use global (more generally namespace scope) data to avoid copying, consider passing the data as a const reference to an object. "
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
Locate guideline I.2 in the C++ Core Guidelines and review the sentence quoted in the issue. Update the wording to the proposed “a const reference to an object” phrasing if it remains appropriate, then verify the surrounding guideline text remains consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100