Dismantling requirements tables 29-36
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
To convert the lib-intro requirements tables 29-36 into paragraphs, we don't currently have any section, and no good way to reference them.
Idea:
- A new subsection "16.4.4.?: Basic type requirements", after [16.4.4.2, utility.arg.requirements] and before [16.4.4.3, swappable.requirements].
- New nested subsections for each individual requirement, so that we can reference them individually (which is currently possible via the tables).
Thoughts?
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 locating lib-intro requirements tables 29-36 and compare them with sections 16.4.4.2, utility.arg.requirements, and 16.4.4.3, swappable.requirements. Review how nearby requirements are structured and referenced, then confirm the subsection placement and naming with maintainers. Done means the tables are represented as individually referenceable paragraphs or nested subsections without gaps in the surrounding structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, tex
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100