[Bug libstdc++/115514] Nonconforming reverse_iterator::operator->

2024-06-18 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115514 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/115514] Nonconforming reverse_iterator::operator->

2024-06-18 Thread de34 at live dot cn via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115514 Jiang An changed: What|Removed |Added CC||de34 at live dot cn --- Comment #3 from Jian

[Bug libstdc++/115514] Nonconforming reverse_iterator::operator->

2024-06-18 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115514 --- Comment #2 from Jonathan Wakely --- The constraint on reverse_iterator::operator->() checks it for an lvalue, which suggests nobody considered (or cared) about annoying iterators that do something different for lvalues and rvalues. I'm incl

[Bug libstdc++/115514] Nonconforming reverse_iterator::operator->

2024-06-18 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115514 --- Comment #1 from Jonathan Wakely --- (In reply to frankhb1989 from comment #0) > (Another difference is it only applies the resolution for C++17 onward.) C++20 onward, I think.