https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111861
--- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Patrick Palka <[email protected]>: https://gcc.gnu.org/g:3268c47c08782efe7fb1dd9a110bebe018e7d59c commit r16-3933-g3268c47c08782efe7fb1dd9a110bebe018e7d59c Author: Patrick Palka <[email protected]> Date: Wed Sep 17 14:14:37 2025 -0400 libstdc++/ranges: Fix more wrong value type init from reference type [PR111861] As in r16-3912-g412a1f78b53709, this fixes some other spots where we wrongly use a deduced type and non-direct-initialization when trying to initialize a value type from an iterator's reference type. PR libstdc++/111861 libstdc++-v3/ChangeLog: * include/bits/ranges_algo.h (ranges::unique_copy): When initializing a value type object from *iter, use direct-initialization and don't use a deduced type. (ranges::push_heap): Use direct-initialization when initializing a value type object from ranges::iter_move. (ranges::max): As in ranges::unique_copy. * include/bits/ranges_util.h (ranges::min): Likewise. Reviewed-by: Jonathan Wakely <[email protected]>
