P4037R1 Supporting `signed char` And `unsigned char` In `<random>`
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
WG21-P4037R1 Supporting signed char And unsigned char In <random>
This paper says:
No feature-test macro is provided because these changes are intended to be applied as a defect report.
When this paper was accepted at the 2026-03 meeting in Croydon, it wasn't formally voted in as a Defect Report, but I believe that it should be treated as a de facto DR, implemented unconditionally (i.e. all the way down to C++14).
We also have a bunch of obnoxious workarounds in our tests and benchmarks that can be removed.
Contributor guide
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 WG21-P4037R1 and locating the implementation, then inspect the tests and benchmarks that contain workarounds for signed char and unsigned char. Done means those types are supported unconditionally through C++14 and the obsolete workarounds are removed, with the affected tests and benchmarks passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100