gt; + operator()(_Iter __first, _Sent __last, const _Tp& __value, _Proj
> > > __proj = {}) const
> > > + { return ranges::find(std::move(__first), __last, __value, __proj)
> > > != __last; }
> >
> > Should this use std::move(__proj)?
>
> Oo
_Tp*>
> > + constexpr bool
> > + operator()(_Iter __first, _Sent __last, const _Tp& __value, _Proj
> > __proj = {}) const
> > + { return ranges::find(std::move(__first), __last, __value, __proj)
> > != __last; }
>
> Should this use std::move(__
On Mon, 14 Nov 2022 at 04:51, Patrick Palka via Libstdc++
wrote:
>
> Tested on x86_64-pc-linux-gnu, does this look OK for trunk?
>
> libstdc++-v3/ChangeLog:
>
> * include/bits/ranges_algo.h (__contains_fn, contains): Define.
> (__contains_subrange_fn, contains_subrange): Define.
>
Tested on x86_64-pc-linux-gnu, does this look OK for trunk?
libstdc++-v3/ChangeLog:
* include/bits/ranges_algo.h (__contains_fn, contains): Define.
(__contains_subrange_fn, contains_subrange): Define.
* testsuite/25_algorithms/contains/1.cc: New test.
*
