Clarify what the C++ Alliance position in d4238-send-cpp-26-back.md means - #49
Conversation
|
@villevoutilainen see comments from @vinniefalco in the slack (pasted below for convenience)
|
|
Harry has revised wording |
bottha123
left a comment
bottha123
left a comment
There was a problem hiding this comment.
@villevoutilainen @MungoG please take a look
| None of this process broke a rule, which is why the working group cannot catch it from inside: a process built to produce consensus on time will produce it, whether or not the underlying design was audited. The one audit that ISO places outside the working group is the National Body ballot, and the C++ Alliance's position is that the National Bodies vote No on the C++26 DIS ballot, with technical comments, and return the draft for the evaluation it skipped, at the cost of one cycle. The same procedural maneuvers are being practiced again on a successor proposal, so the ballot check should be exercised now rather than deferred to a later cycle. | ||
|
|
||
| The authors provide information and serve at the pleasure of the committee. The authors of P4238R0 request no floor time, no poll, and no committee action; they state a position and offer two recommendations to the National Bodies and the convener. | ||
|
|
There was a problem hiding this comment.
The C++ Alliance maintains a governance research program that analyzes the effectiveness of WG21 C++ standardization: its procedures, its consensus practices, and its output. When the Alliance publishes an official position on committee matters, that position reflects the findings of this research program. It does not represent a poll of Alliance staff, nor does it bind the personal views of any engineer, contractor, or board member.
There was a problem hiding this comment.
Looks good to me, ship it.
| The paper communicates the position of the C++ Alliance, while pointing out that that is not necessarily the position of every individual working for or otherwise sponsored by the C++ Alliance. | ||
|
|
|
@villevoutilainen as these are Harry's suggested changes to your PR, you need to make the changes on your branch. |
4 participants
No description provided.