Date: Wed, 05 Oct 2022 03:53:56 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 266834] clang: search doesn't work for filesystem::path in clang-14 Message-ID: <bug-266834-29464-4zI50ZalPr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266834-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-266834-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266834 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #2 from Mark Millard <marklmi26-fbsd@yahoo.com> --- 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=3D=3Di1 . 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. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-266834-29464-4zI50ZalPr>