On Fri, 26 Aug 2022 at 21:05, Jonathan Wakely wrote:
>
> On Tue, 23 Aug 2022 at 02:38, Patrick Palka via Libstdc++
> <libstd...@gcc.gnu.org> wrote:
> > + template<typename _Fp, typename _Tuple>
> > + constexpr void
> > + __tuple_for_each(_Fp&& __f, _Tuple&& __tuple)
> > + {
> > + std::apply([&]<typename... _Ts>(_Ts&&... __elts) {
> > + (std::__invoke(__f, std::forward<_Ts>(__elts)), ...);
> > + }, std::forward<_Tuple>(__tuple));
>
>
> Nicole Mazzuca noticed a problem with the definition of
> tuple-for-each, which I've just added to the issues list:
> https://cplusplus.github.io/LWG/issue3755
Ignore this. The __tuple_for_each function is only ever called by the
library, so there's no way for something like Evil to be passed to it.
