isocpp / isocpp/CppCoreGuidelines
File extensions for modules?
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 45.3k
- Forks
- 5.6k
- PR merge metrics
- No merged PRs in 30d
Description
https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#nl27-use-a-cpp-suffix-for-code-files-and-h-for-interface-files already exists for old-style code using cpp/h files. However, there is no rule for file extensions related to modules. This is primarily important when having a codebase that mixes both behaviors.
It seems we already are introducing several extensions depending on the compiler. (Ref: https://stackoverflow.com/a/76422027/2466431)
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
Read rule NL27 in the C++ Core Guidelines and review the linked Stack Overflow discussion about compiler-dependent module extensions. Done would require an agreed guideline for module-related file extensions that addresses codebases mixing modules with traditional .cpp and .h files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100