[Bug libstdc++/108952] Regression in uses_allocator_construction_args for pair of rvalue references
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108952 --- Comment #5 from Jonathan Wakely --- (In reply to Peter Dimov from comment #4) > An easy fix is to use `std::get<0>` instead of `.first`. Yeah I tried that, but I think there's an additional change needed (or I messed something up).
[Bug libstdc++/108952] Regression in uses_allocator_construction_args for pair of rvalue references
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108952 Peter Dimov changed: What|Removed |Added CC||pdimov at gmail dot com --- Comment #4 from Peter Dimov --- An easy fix is to use `std::get<0>` instead of `.first`.
[Bug libstdc++/108952] Regression in uses_allocator_construction_args for pair of rvalue references
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108952 TC changed: What|Removed |Added CC||rs2740 at gmail dot com --- Comment #3 from TC --- https://cplusplus.github.io/LWG/issue3527
[Bug libstdc++/108952] Regression in uses_allocator_construction_args for pair of rvalue references
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108952 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org Ever confirmed|0 |1 Last reconfirmed||2023-02-27 --- Comment #2 from Jonathan Wakely --- The problem is that std::move(pr).first always yields an lvalue, even if the type of pr is pair. I tried to simplify uses_allocator_construction_args to avoid indirection, which I think is the source of this issue.
[Bug libstdc++/108952] Regression in uses_allocator_construction_args for pair of rvalue references
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108952 --- Comment #1 from Andrew Pinski --- Created attachment 54546 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54546=edit testcase Please next time also attach or put inline the testcase