> From: Jonathan Wakely <jwak...@redhat.com> > Date: Thu, 23 Nov 2023 17:51:38 +0000
> libstdc++-v3/ChangeLog: > > PR libstdc++/111055 > * include/bits/ranges_base.h (from_range_t): Define new tag > type. > (from_range): Define new tag object. > * include/bits/version.def (ranges_to_container): Define. > * include/bits/version.h: Regenerate. > * include/std/ranges (ranges::to): Define. > * testsuite/std/ranges/conv/1.cc: New test. > * testsuite/std/ranges/conv/2_neg.cc: New test. > * testsuite/std/ranges/conv/version.cc: New test. JFTR, for the list: this (r14-5794-g7a6a29c455e775) caused another one of those wonderful "xtreme test" regressions. Logged as PR112737: "[14 Regression] g++.dg/modules/xtreme-header-2_b.C -std=c++2b (test for excess errors)", and pinskia quickly linked it to the meta-bug for modules issues, PR103524 (thanks!) IIRC, sometimes those tests show bugs elsewhere, suggesting lack of coverage in other tests (and not just streaming aspects), but this one actually mentions modules in key error messages. brgds, H-P