[Bug libstdc++/107850] [12/13 Regression] std::erase_if (map) forces predicate to takes a const value_type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107850 --- Comment #3 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:f54ceb2062c7fef294f85ae093914fa6c7ca35b8 commit r13-4306-gf54ceb2062c7fef294f85ae093914fa6c7ca35b8 Author: Jonathan Wakely

[Bug libstdc++/107850] [12/13 Regression] std::erase_if (map) forces predicate to takes a const value_type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107850 Jonathan Wakely changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org

[Bug libstdc++/107850] [12/13 Regression] std::erase_if (map) forces predicate to takes a const value_type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107850 --- Comment #2 from Jonathan Wakely --- I have very little sympathy for this use case, predicates that can't be called with const arguments are always wrong. I'm inclined to say the standard should be fixed to match our new behaviour.

[Bug libstdc++/107850] [12/13 Regression] std::erase_if (map) forces predicate to takes a const value_type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107850 Andrew Pinski changed: What|Removed |Added Summary|std::erase_if (map) forces |[12/13 Regression]