-
Notifications
You must be signed in to change notification settings - Fork 771
Issues: cplusplus/draft
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[unreachable.sentinel] Incorrect usage example of std::unreachable_sentinel
lwg
Issue must be reviewed by LWG.
not-editorial
Issue is not deemed editorial; the editorial issue is kept open for tracking.
#7859
opened Apr 29, 2025 by
xmcgcg
[derivation] Do we need to clarify "all types specified in the C++ standard library"?
#7858
opened Apr 27, 2025 by
frederick-vs-ja
[temp.func.order] Making the intent of transformations clearer
#7855
opened Apr 24, 2025 by
seha-bot
[intro.compliance.general], [using.headers] Redundant and inconsistent wording
#7846
opened Apr 21, 2025 by
Eisenwave
[expos.only.entity] Should we use
iter-value-type
in more places?
#7844
opened Apr 19, 2025 by
frederick-vs-ja
[lex.pptoken] "Whitespace" and "whitespace characters" should be definitions
#7842
opened Apr 16, 2025 by
Eisenwave
[basic.contract.eval] A note becomes incorrect after adopting P3471R4
#7775
opened Mar 25, 2025 by
xmcgcg
[assertions.assert] The meaning of "standard error stream" is unclear
#7760
opened Mar 22, 2025 by
frederick-vs-ja
Reword "possible to be well-defined only if" wording in "sized ranges" notes
#7737
opened Mar 15, 2025 by
tkoeppe
[deque.modifiers] Clarify complexity requirements on deque insertion
#7732
opened Mar 12, 2025 by
RedBeard0531
[class.prop] standard-layout class type requirements are hard to read
#7593
opened Jan 28, 2025 by
Eisenwave
[expr.prim.lambda.closure] Ambiguous parsing of implementation freedom
#7570
opened Jan 17, 2025 by
brevzin
Previous Next
ProTip!
Adding no:label will show everything without a label.