<format>: better exceptions
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 11.2k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
<format> currently just throws std::format_errors with vague strings describing what went wrong, we may be able to enhance these error messages to contain more useful information, such as the format argument involved or the parsed format specs.
It may or may not be worth making these enhancements, particularly after WG21-P2216 is applied (compile time format string checks)
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 reviewing the implementation and its current std::format_error paths, then read WG21-P2216 to understand the stated context. The issue does not name files or tests; completion would require deciding whether richer exception messages are worthwhile and defining the information they should contain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100