[Bug libstdc++/81482] by-value lambda capture in remove_if

2024-03-14 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81482 Andrew Pinski changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED

[Bug libstdc++/81482] by-value lambda capture in remove_if

2017-08-10 Thread fabian-gcc at kloetzl dot info
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81482 --- Comment #4 from kloetzl --- > And changing the algorithm to make no copies would not make it opaque, because > the lack of copies would be observable. As the standard says, whether copies > are made or not is unspecified. So if you want to tr

[Bug libstdc++/81482] by-value lambda capture in remove_if

2017-08-04 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81482 --- Comment #3 from Jonathan Wakely --- (In reply to kloetzl from comment #2) > I don't think that the runtime cost of the copies is measurable. My bigger > issue is that this quirks exposes the internal behaviour of the algorithm > implementatio

[Bug libstdc++/81482] by-value lambda capture in remove_if

2017-08-03 Thread fabian-gcc at kloetzl dot info
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81482 --- Comment #2 from kloetzl --- I don't think that the runtime cost of the copies is measurable. My bigger issue is that this quirks exposes the internal behaviour of the algorithm implementation; In this case the fact that remove_if calls find_i

[Bug libstdc++/81482] by-value lambda capture in remove_if

2017-07-21 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81482 Jonathan Wakely changed: What|Removed |Added Severity|normal |minor --- Comment #1 from Jonathan Wak