Date: Sat, 2 Nov 2024 23:44:58 +0100
On 02/11/2024 18.28, mauro russo wrote:
> *) Despite it is ok to me not considering the 'note' that I proposed in the original email, I still see valuable to refer [temp.spec.partial.ordering] from the extended text in [temp.spec.partial.general]-1, just as it refers [temp.spec.partial.match].
[temp.spec.partial.match] does refer to [temp.spec.partial.order].
Also note that the definition for ambiguity is in [temp.spec.partial.match],
not in [temp.spec.partial.ordering].
> *) how it works about eventually applying the change also for previous standard versions ? Is it really possible ?
It is possible to publish a Technical Corrigendum for the current
standard, which is C++23. Versions before that are withdrawn,
and changing them is not possible.
WG21 has never published a Technical Corrigendum, and given the
three-year cadence in which we publish standards, it's unlikely
we'll ever do so. (The next standard will arrive too soon to
make a Technical Corrigendum worth the effort.)
Jens
> *) Despite it is ok to me not considering the 'note' that I proposed in the original email, I still see valuable to refer [temp.spec.partial.ordering] from the extended text in [temp.spec.partial.general]-1, just as it refers [temp.spec.partial.match].
[temp.spec.partial.match] does refer to [temp.spec.partial.order].
Also note that the definition for ambiguity is in [temp.spec.partial.match],
not in [temp.spec.partial.ordering].
> *) how it works about eventually applying the change also for previous standard versions ? Is it really possible ?
It is possible to publish a Technical Corrigendum for the current
standard, which is C++23. Versions before that are withdrawn,
and changing them is not possible.
WG21 has never published a Technical Corrigendum, and given the
three-year cadence in which we publish standards, it's unlikely
we'll ever do so. (The next standard will arrive too soon to
make a Technical Corrigendum worth the effort.)
Jens
Received on 2024-11-02 22:45:04