[Bug c++/121327] Not-matching concept fails to compile with error "depends on itself"

2025-07-30 Thread b.stanimirov at abv dot bg via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121327 --- Comment #1 from Borislav Stanimirov --- So, the problem is that `std::equality_comparable_with` is bidirectional. It checks lhs==rhs and rhs==lhs. Using it with two id types will lead to an infinite recursion of checking `rhs==X`. The reaso

[Bug c++/121327] New: Not-matching concept fails to compile with error "depends on itself"

2025-07-30 Thread b.stanimirov at abv dot bg via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121327 Bug ID: 121327 Summary: Not-matching concept fails to compile with error "depends on itself" Product: gcc Version: 16.0 Status: UNCONFIRMED Severity: normal

[Bug c++/121122] New: -Wdangling-reference false postitive when adding a non-dangling reference to the mix

2025-07-16 Thread b.stanimirov at abv dot bg via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121122 Bug ID: 121122 Summary: -Wdangling-reference false postitive when adding a non-dangling reference to the mix Product: gcc Version: 16.0 Status: UNCONFIRMED Sev

[Bug tree-optimization/104165] [12 Regression] -Warray-bounds for unreachable code inlined from std::sort()

2025-06-24 Thread b.stanimirov at abv dot bg via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104165 Borislav Stanimirov changed: What|Removed |Added CC||b.stanimirov at abv dot bg --- Co

[Bug libstdc++/108714] New: Algorithms in require predicates to be copyable

2023-02-08 Thread b.stanimirov at abv dot bg via Gcc-bugs
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:

[Bug libstdc++/108118] New: std::weak_ptr lacks a self-usurp check on move

2022-12-15 Thread b.stanimirov at abv dot bg via Gcc-bugs
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

[Bug libstdc++/98473] std::vector::insert(pos, first, last) doesn't compile for T which has a deleted assignment operator

2021-01-04 Thread b.stanimirov at abv dot bg via Gcc-bugs
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.

[Bug libstdc++/98473] std::vector::insert(pos, first, last) doesn't compile for T which has a deleted assignment operator

2021-01-01 Thread b.stanimirov at abv dot bg via Gcc-bugs
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

[Bug libstdc++/98473] New: std::vector::insert(pos, first, last) doesn't compile for T which has a deleted assignment operator

2020-12-29 Thread b.stanimirov at abv dot bg via Gcc-bugs
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