C++ module readiness
Open
Nobody has claimed this yet.
feature-request
- Dominant language
- C++
- Stars
- 3k
- Forks
- 300
- Avg merge
- 19h 12m
- Merged PRs (30d)
- 1
Description
As new and modern header only library, what is the direction and thinking behind modules support ? Efforts like cppwirt seem to have been designed for modules . All the more critical if this is going to be the modern header replacement for Windows . Little skeptical here as the project is replete with macros
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
The issue names no files, tests, or entry points. Start by reviewing the module-support discussion and the cppwirt effort mentioned in the issue; the work is not ready to begin until a concrete direction and definition of done are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100