| Issue |
124937
|
| Summary |
[libc++] Strenghten noexcept specification for container move-assignment
|
| Labels |
libc++
|
| Assignees |
|
| Reporter |
ldionne
|
Do we want `is_nothrow_move_assignable<Alloc>` to affect the exception specifications (which potentially weakens exception specifications)?
Note that [[allocator.requirements.general]/84](https://eel.is/c++draft/allocator.requirements.general#84) requires that if the allocator is move-assigned, the operation must not throw an exception, even if the move assignment is potentially throwing.
_Originally posted by @frederick-vs-ja in https://github.com/llvm/llvm-project/pull/120312#discussion_r1889454171_
![]()
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
