How to represent header-only libraries
Open
documentation
scheduled
- Dominant language
- Python
- Stars
- 191
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
It seems odd to call them an `Interface`, but there doesn't seem to be another way to represent them
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the Common Package Specification and how it currently represents Interface components, then compare that model with the needs of header-only libraries. Done means reaching and documenting a decided representation rather than leaving the issue as an open question.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100