-
Notifications
You must be signed in to change notification settings - Fork 1
P1729 R5 Text Parsing #493
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
Comments
LEWG-I wants first crack at this. |
P1729R0 Text Parsing: Direction Review Champion: Victor Zverovich Minute Taker: Elias Kosunen Start Overview: 07-15 11:00 We probably can't call this SG16 needs to review this. Is the extension API essential for version 1? Start Review: 11:16 Hana: How do you handle greediness? Chris Kennelly: How much implementation experience do you have? Adrian: Two things that this thing does: extract of strings, and conversion of strings to other types. Start Polling: 11:27 POLL: We should promise more committee time to pursuing P1729R0, knowing that our time is scarce and this will leave less time for other work. NO OBJECTION TO UNANIMOUS CONSENT. Attendance: 15 End: 11:29 CONSENSUS: Bring a revision of P1729R0, exploring different approaches for outputs (e.g. output parameters, tuple-like return values), to LEWGI for further design review. |
SG16 2019-07 review in Cologne No polls taken. The author was present. Dropping the SG16 label and looking forward to a future revision. |
P1729R1 Text Parsing (Victor Zverovich , Elias Kosunen) |
P1729R1 Text Parsing: Design Review Champion: Victor Zverovich Minute Taker: Ben Craig Start Review: 11-04 13:44 Start Polling: 14:50 POLL: Using the same format string for input and output is an important design goal.
Attendance: 14 That has consensus. POLL: We want positional arguments in
Attendance: 14 That has consensus. POLL: We want to require positional arguments to be unique in
Attendance: 14 That has no consensus. Break: 15:23 Resume: 15:45 POLL: Supporting non-DefaultConstructible types is an important design goal.
Attendance: 15 That has no consensus. POLL: Getting the successfully scanned values from partial successes is an important design goal.
Attendance: 14 There is consensus against that. End: 16:34 CONSENSUS: Bring a revision of P1729R1 (Text Parsing), with the guidance below, to LEWGI for further design review.
|
SG16 did not review P1729R1 in Belfast due to time constraints. We'll plan to review in Prague. The author has specifically requested guidance on how to specify and implement skipping of white space for Unicode encodings. |
P1729R2 Text Parsing (Elias Kosunen, Victor Zverovich) |
SG16 began reviewing P1729R2 during its 2023-09-27 meeting. No polls have been taken yet; continued review is planned for the 2023-10-11 SG16 meeting. |
P1729R3 Text Parsing (Elias Kosunen) |
SG16 reviewed a draft of P1729R3 during its 2023-10-11 meeting. We still haven't taken any polls, but the paper has strong support. There are still some questions to be sorted out regarding scanning of text vs binary input. |
P1729R4 Text Parsing (Elias Kosunen, Victor Zverovich) |
SG9 briefly looked at this paper in Tokyo to follow up on our discussion of the paper in Kona. We took the following poll: With the following changes:
Forward P1729R4 to LEWG for inclusion in C++26.
Conclusion: enough of consensus (weak quorum), given the consensus that also existed in Kona We will address the weak quorum by asking the SG9 mailing list to file any objections within the next week, but unless we get such objections (which will be summarized here), the SG9 aspects of this proposal are ready for LEWG review (once other study groups are done with it, of course). |
SG16 reviewed P1729R4 during its 2024-03-13 meeting. No polls were taken. Some questions were raised regarding the proposed Adding the |
P1729R5 Text Parsing (Elias Kosunen, Victor Zverovich) |
@inbal2l, I don't think this paper is on track for C++26. If you agree, please remove the |
P1729R0 Text Parsing (Victor Zverovich)
The text was updated successfully, but these errors were encountered: