On Tue, 17 Mar 2026 at 22:08, Jonathan Wakely <[email protected]> wrote: > > Jakub wrote a plugin which identified some non-reserved names being used > in our headers. The "count" one is actually a reserved name (there's > std::set::count and std::count and std::bitset::count) but we might as > well uglify it when used as a function parameter name. I think the "ext" > ones must have happened when moving function definitions from fs_path.cc > to fs_path.h and I forgot to change them. > > The __cond::wait and __cond::wait_recursive member functions are using > non-reserved names, so that should be changed too, but this patch > doesn't fix that. I don't think we use the __gnu_cxx::__cond type in any > headers, so maybe that should just be moved into libsupc++/guard.cc or a > new header which is not installed and only used while building the > library. > > libstdc++-v3/ChangeLog: > > * include/bits/chrono_io.h (__formatter_duration::_S_subseconds): > Uglify subs variable name. > * include/bits/fs_path.h (path::stem, path::extension) > (path::has_stem, path::has_extension): Uglify ext parameter > name. > * include/ext/concurrence.h (__cond::wait, __cond::wait_recursive): > Uglify mutex parameter names. > * include/pstl/glue_algorithm_defs.h (generate_n): Uglify count > parameter name. > * include/std/ranges (zip_transform_view): Uglify Rs template > parameter name. > (__cartesian_is_sized_sentinel): Uglify FirstSent template > parameter name. > * include/tr1/riemann_zeta.tcc: Uglify max_size variable name.
Oops, that was mean to say "max_iter" not "max_size".
