P2757R3 Type-Checking Format Args
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
WG21-P2757R3 Type-Checking Format Args
LWG-4142 format_parse_context::check_dynamic_spec should require at least one type
INCREASED feature-test macro, note that __cpp_lib_format has repeatedly increased through 202304L (#3799 WG21-P2510R3), 202305L (#3813 WG21-P2757R3), 202306L (#3808 WG21-P2637R3), 202603L (#4181 WG21-P2918R2):
#define __cpp_lib_format 202305L // <== NOTE SPECIAL VALUE
Note: We are not yet accepting PRs for C++26 features.
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
Begin by reading WG21-P2757R3 and LWG-4142, then locate the existing format implementation and its feature-test macro. The issue names no files or tests; completion would require implementing the specified type-checking behavior and reflecting the 202305L __cpp_lib_format value, subject to the note about C++26 PRs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100