isocpp / isocpp/CppCoreGuidelines
There is a need for a guideline regarding C names in the std namespace?
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 45.3k
- Forks
- 5.6k
- PR merge metrics
- No merged PRs in 30d
Description
There is a need for a guideline regarding C names in the std namespace?
- No need to mention it, it doesn't matter if you use size_t (::size_t?)
- The guidelines should explicitly recommend std::size_t?
- The guidelines should explicitly say it doesn't matter?
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
The issue does not name a file, test, or entry point. Review the existing C++ naming guidance and the discussion around global versus std:: names, then document a clear recommendation for size_t usage; done means the guideline resolves the listed alternatives explicitly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100