https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108714
Bug ID: 108714
Summary: Algorithms in require predicates to be
copyable
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108118
Bug ID: 108118
Summary: std::weak_ptr lacks a self-usurp check on move
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98473
--- Comment #3 from Borislav Stanimirov ---
By the way, this is not just some esoteric synthetic example. A type which is
copy-constructible but not copy-assignable is very useful to model immutable
objects.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98473
--- Comment #2 from Borislav Stanimirov ---
(In reply to Jonathan Wakely from comment #1)
> To meet the requirements of the standard we would need to insert them at the
> end and then use std::rotate to reposition them.
Or, to save move assignm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98473
Bug ID: 98473
Summary: std::vector::insert(pos, first, last) doesn't
compile for T which has a deleted assignment operator
Product: gcc
Version: unknown
Status: UNCONFIRM