extra_includes for templates
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 7
- Forks
- 3
- Avg merge
- 18h 33m
- Merged PRs (30d)
- 7
Description
Since each template instantiation is built in its own translation unit, being able to have different includes for each template instantiation would be beneficial.
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 tracing how semiwrap handles template instantiations and creates their separate translation units; the payload does not identify a file, test, or entry point. Determine where per-instantiation include configuration belongs, then add coverage showing that different template instantiations receive their requested includes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100