-
Notifications
You must be signed in to change notification settings - Fork 18
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
P1467 Extended floating-point types and standard names #227
Comments
SG6: Define narrowing conversions on rank instead of finite value ranges? Make rank of overlapped ranges unordered. Make operations on unordered ranks ill-formed. |
Lots of feedback in EWG-I in Kona. Want to see again. LEWGI should see this too. |
P1467R1 Extended floating-point types (Michał Dominiak, David Olsen) |
P1467R1 Extended Floating Point Types: Design Review Champion: Michał Dominiak Minute Taker: Jayesh Badwaik Start Overview: 07-16 10:42 Start Review: 11:02 Make sure outputting extended floating point types with iostreams works. Is a type trait needed for determining floating-point conversion rank? Do we need any new type traits for floating point types in this brave new world? Put the P1468R1 Fixed-Layout Floating Point Type Aliases: Design Review Champion: Michał Dominiak Minute Taker: Jayesh ? Start Overview: 07-16 11:38 Start Review: 11:42 Start Polling: 11:48 POLL: Fixed-type floating point types are allowed to alias
Attendance: 26 This has strong consensus. POLL: Have the fixed-layout floating point types only be declared if they are available, and have feature test macros for each type. NO OBJECTION TO UNANIMOUS CONSENT. Attendance: 25 POLL: Forward P1467R0 (with the addition of support for extended floating point types in
A: Want to see more implementation experience. Attendance: 25 End: 12:04 CONSENSUS: Forward P1467R0 (with the addition of support for extended floating point types in |
EWGI in Cologne (seen with #228): The extended floating-point types should be allowed to alias float/double/long double. Note one of the above polls reverse a LEWGI poll. Send to EWG + LEWG. |
CWG telecon 2022-02-25: Partially reviewed. |
Poll outcome:✅ consensus |
CWG telecon 2022-03-11: Partially reviewed. |
CWG telecon 2022-03-25: Reviewed D1467R9; two small updates have been requested. |
CWG telecon 2022-04-08: Reviewed updated D1467R9; an update regarding the phrasing for floating-point types as vendor extensions has been requested. |
CWG telecon 2022-04-22: Approved D1467R9 for plenary vote. |
I"m noticing the LWG notes didn't get added here. https://wiki.edg.com/bin/view/Wg21telecons2022/P1467-20220225 LWG saw this over 3 sessions and asked for various refinements that were made -- culminating in a vote on 2022-04-01 P1467r9 to be sent to Core for inclusion into C++23 with the small amendment discussed?
|
P1467R9 Extended floating-point types and standard names (David Olsen, Michał Dominiak, Ilya Burylov) |
@jensmaurer and @jwakely -- did we decide if this is CWG or LWG motion? |
@jensmaurer and @jwakely agreed that this paper would be a CWG motion, since the core changes are more significant than the library changes. |
It's on the list of CWG proto-motions: https://wiki.edg.com/bin/view/Wg21telecons2022/StagingForPlenaryStrawPolls |
P1467R0 Extended floating-point types (Michał Dominiak, David Olsen)
The text was updated successfully, but these errors were encountered: