Created on 2019-02-10.00:00:00 last changed 12 months ago
[ 2023-12-22; Daniel comments ]
This issue should be resolved by LWG 4028.
[ 2020-03-11 Issue Prioritization ]
Priority to 3 after reflector discussion.
[ 2020-02-22, Daniel comments ]
This seems to be quite related to the existing issue LWG 2116.
This issue was submitted after a previous editorial change request had been rejected by the project editors.
I find that all known implementations (at least msvcstl, libc++, libstdc++ and the sample in P0758R1) of std::is_nothrow_convertible may be not clear enough to indicate that whether destruction of the destination type is considered (or not). For example, given a type Weird defined asstruct Weird { Weird(int) noexcept {} ~Weird() noexcept(false) {} };
Then std::is_nothrow_convertible_v<int, Weird> is false in every known implementation. However, it seems that the conversion itself is noexcept.
History | |||
---|---|---|---|
Date | User | Action | Args |
2023-12-22 12:45:58 | admin | set | messages: + msg13899 |
2020-03-11 18:59:36 | admin | set | messages: + msg11162 |
2020-02-22 10:19:06 | admin | set | messages: + msg11135 |
2019-02-10 00:00:00 | admin | create |