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
LWG3810 CTAD for std::basic_format_args #1368
Comments
2023-01-10 Library Evolution TeleconLWG3810: CTAD for 2023-01-10 Library Evolution Telecon Minutes Chair: Bryce Adelstein Lelbach Minute Taker: Ben Craig Start: 2023-01-10 11:58 Eastern POLL: Send the proposed resolution to LWG3810 (CTAD for
Attendance: 13 # of Authors: 0 Author Position: N/A Outcome: Unanimous consensus in favor. End: 12:01 Next StepsTake a Library Evolution electronic poll to send the proposed resolution to LWG3810 (CTAD for |
We only have two C++23 papers that need electronic polling, and both were non-controversial. I'm going to send this directly to Library. |
poll: approve the resolution for LWG3810 and move to immediate? https://wiki.edg.com/bin/view/Wg21issaquah2023/LWG3810-202306
|
This should have been fixed by cplusplus/draft#6116. |
https://cplusplus.github.io/LWG/issue3810
LWG would like design guidance here. Should CTAD work? It's currently sort-of implied it should, but only if you assume that the exposition-only types and constructors are implemented exactly as shown. If the
format-arg-store
-type is defined as a nested type ofbasic_format_args
(as in libstdc++) then it doesn't work.There's an example from Tomasz in the issue showing a case where CTAD might be useful, but Victor suggested we should explicitly disable CTAD here, because it makes it easier to create dangling references.
The text was updated successfully, but these errors were encountered: