You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many functions of volatile were deprecated in C++20. In C++23, volatile compound operations were de-deprecated by P2327. The rationale for this de-deprecation is lacking.
Deprecation is not removal. P2327 in C++23 is stopping the change that we began with C++20, mere moments ago if counting by adoption time. It primarily argued that it’s an inconvenient change, and that some of the audience would just not cooperate with WG21’s indicated direction, so WG21 should compromise the technical consistency of the Standard so they could continue to not cooperate.
The paper did not bring new information on the technical merits of the case, and net the result of applying it was a technically dissonant Standard specification — a strictly worse specification than C++20. Bitwise compound operations are not special for any technical reason, they are only special because making them special shields some from deprecation diagnostics.
Proposed change:
Revert P2327, which de-deprecated volatile compound operations.
The text was updated successfully, but these errors were encountered:
jensmaurer
changed the title
US 7.6.19 [expr.ass] Revert de-deprecation of certain compound volatile assignments
US 16-045 7.6.19 [expr.ass] Revert de-deprecation of certain compound volatile assignments
Nov 3, 2022
CWG 2022-11-08: Accepted with Modifications. Restored consistency by un-deprecating all volatile compound assignment operations; see CWG2654 for details.
Many functions of volatile were deprecated in C++20. In C++23, volatile compound operations were de-deprecated by P2327. The rationale for this de-deprecation is lacking.
Deprecation is not removal. P2327 in C++23 is stopping the change that we began with C++20, mere moments ago if counting by adoption time. It primarily argued that it’s an inconvenient change, and that some of the audience would just not cooperate with WG21’s indicated direction, so WG21 should compromise the technical consistency of the Standard so they could continue to not cooperate.
The paper did not bring new information on the technical merits of the case, and net the result of applying it was a technically dissonant Standard specification — a strictly worse specification than C++20. Bitwise compound operations are not special for any technical reason, they are only special because making them special shields some from deprecation diagnostics.
Proposed change:
Revert P2327, which de-deprecated volatile compound operations.
The text was updated successfully, but these errors were encountered: