consider whether [cinttypes.syn] is in the right place
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
<cinttypes> is a weird header. It contains abs and div for intmax_t, plus some primitive string <-> integer conversion functions. And some printf / scanf format string macros. And we put it in the iostreams portion of the standard.
Is this really best?
We once kept all the formatting and parsing stuff within [input.output], but now we have [charconv], and somewhere near there seems like a much better fit for the primitive formatting and parsing functions in .
The integer div / abs functionality seems to belong in [numerics].
The format string macros seem to belong near [cstdio.syn], which is where the header currently is.
And maybe we could "compromise" and put the header in [cstdint].
So: I'm not sure what's best, but we should talk about it some more, especially given that the advent of [charconv] significantly weakens the argument for the current home.
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
Read [cinttypes.syn] alongside [charconv], [numerics], [cstdio.syn], and [cstdint], then review its current placement within [input.output]. Done means reaching and documenting a consensus on the organization of the header's facilities and updating the relevant standard structure accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, tex
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100