[allocator.traits.other] uses "above" to reference something 14 pages before it
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
The definition of allocation_result is in [memory.syn] (page 598 in my PDF), while this subclause is on page 612. It may be better to either move the only paragraph after the <memory> synopsis or move the allocation_result definition into [allocator.traits.other] (leaving just the declaration in the synopsis). The latter may be preferable given how long the <memory> synopsis is.
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
Compare the allocation_result definition in memory.syn with the allocator.traits.other subclause and the surrounding synopsis, using the cited PDF pages to confirm the current ordering. Decide which relocation best removes the distant “above” reference, then verify that the declaration and definition remain correctly placed and the draft builds without the ambiguous cross-reference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tex
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100