C++ Logo


Advanced search

Re: Noexcept specification of basic_string's move assignment operator in C++11 and C++14

From: Bo Persson <bo_at_[hidden]>
Date: Sat, 22 Feb 2020 13:14:06 +0100
On 2020-02-21 at 12:52, Giuseppe D'Angelo via Std-Discussion wrote:
> Il 21/02/20 11:25, Daniel Kr├╝gler via Std-Discussion ha scritto:
>>> OK. Can we say it was*against* C++11 but then it was only resolved for
>>> C++17?
>> Yes. AFAIK, there exists no defined process for the standard that
>> applies fixes made in a later standard to previous standards.
> However, in general, aren't defect resolutions supposed to be applied
> retroactively? Sure, are no means to republishing an already-issued
> Standard including the resolutions; but implementations are supposed to
> pick them up.

 From an ISO perspective there is only one standard - the current release.

When C++17 was published, C++14 was formally withdrawn.


So what does it mean to be compliant with a standard revision that
formally doesn't exits anymore? :-)

     Bo Persson

Received on 2020-02-22 06:16:54