https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266834
Mark Millard <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Mark Millard <[email protected]> --- It seems highly unlikely that a C++ standard would be adjusted to require std::search to work on iterators where *i0 and *i1 could be bound to different objects but have i0==i1 . But path::iterator's are explicitly allowed to have this property. Unless a vintage of the language standard changes either the path::iterator's requirements or the search's allowed requirements, expect variability in implementations --without the variations being violations of the standard's criteria. Summary: It looks to be just another example of an Implementation-Defined aspect of the langauge. There are lots of them that lead to non-portable but standard-compliant source code being possible. It is an example of a reason that C++ code that is intended to be rather portable should be explicitly checked against multiple, distinct C++ implementations. -- You are receiving this mail because: You are the assignee for the bug.
