[temp.inst] Specializations can be implicitly instantiated infinitely
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
This is really on the edge of being editorial, but I think it still qualifies.
According to the wording in [temp.inst], a specialization of a template is instantiated when it is not explicitly specialized and not explicitly instantiated. However, there is no mention of what will happen if the specialization has already been implicitly instantiated, which according to the wording would be implicitly instantiated again. I do not believe that this is the intended effect, since it allows multiple definitions of a specialization to be generated in a single translation unit.
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 the [[temp.inst]] wording linked in the issue and examine how it describes implicit instantiation of an already-instantiated specialization. Done means clarifying the standard wording so a specialization cannot be implicitly instantiated repeatedly within one translation unit.
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
- Mostly clear
- Newbie friendliness
- 30/100