clarify meaning of "has an interface dependency [...] prior to X"
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
The phrase "has an interface dependency [...] prior to X" appears in [module.reach]p1 and [basic.start.dynamic]p1, but isn't defined. Per [module.import]p7, "has an interface dependency on" is a relation between translation units, with no associated "location" to be prior to.
It's obvious what it means: the interface dependency is caused by some construct (in this case, a module-declaration or module-import-declaration) that appears prior to X. But we should say that!
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
Start by reading [module.reach]p1, [basic.start.dynamic]p1, and the definition in [module.import]p7. Trace how the phrase is used and clarify that the interface dependency is caused by a module-declaration or module-import-declaration appearing prior to X. Done means the wording explicitly defines the intended location relationship.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100