-
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
P3081 R0 Core safety Profiles: Specification, adoptability, and impact #2058
Comments
SG15 and SG23: please consider and forward to EWG. |
SG15 wants to pursue normatively requiring implementations to offer some specific “Fix” semantics as described in P3081R0, such as “when type_safety profile is enabled, a static_cast pointer downcast remains static_cast in the source code but is interpreted as-if the code had written dynamic_cast” — SG15 will separately describe how implementations could conform
SG15 wants to pursue normatively requiring implementations to offer some specific “Modernize” fixits (as a new form of diagnostic) as described in P3081R0, such as “when type_safety profile is enabled, for a static_cast pointer downcast offer a mechanical fixit to change the source code into a dynamic_cast” — SG15 will separately describe how implementations could conform
|
P3081R0 was seen in SG23 on Thurs in Wroclaw POLL: Apply the SG23 syntax decisions (Weds) in Wrocław and other SG23 direction to P3081R0, and forward P3081 to EWG as part of an initial set of Profiles targeting C++26.
|
Seen in EWG on Friday: Poll: P3081r0 Core safety Profiles, we are interested in pursuing profiles in the C++26 timeline, including aspects of the specification which potentially have language and library impact (i.e. despite the P1000 schedule).
Result: consensus in favor EWG will perform telecons (@hanickadot) between now and the next meeting to discuss individual profile aspects. |
EWG seen first section of paper's wording on 2024/12/11 telecon and took (non-binding, temperature in the room) following polls: D3081R1: The profile attributes
Result: Consensus D3081R1: The next revision of P3081 should explore, clarify, and justify the application of profile attributes on lexical vs declaration scoping.
Result: Consensus D3081R1: EWG prefers that profile attributes include the
Result: Not consensus |
P3081R0 Core safety Profiles: Specification, adoptability, and impact (Herb Sutter)
The text was updated successfully, but these errors were encountered: