Skip to content

[alg.min.max] hasn't been updated when LWG3180 has been applied #5375

Closed
@philnik777

Description

@philnik777

LWG3180 states that [alg.min.max] should be updated to reflect the changes in [algorithm.syn].
The declarations of ranges::minmax_element in [alg.min.max] should be:

template<forward_­iterator I, sentinel_­for<I> S, class Proj = identity,
         indirect_­strict_­weak_­order<projected<I, Proj>> Comp = ranges::less>
  constexpr ranges::minmax_element_result<I>
    ranges::minmax_element(I first, S last, Comp comp = {}, Proj proj = {});
template<forward_­range R, class Proj = identity,
         indirect_­strict_­weak_­order<projected<iterator_t<R>, Proj>> Comp = ranges::less>
  constexpr ranges::minmax_element_result<borrowed_iterator_t<R>>
    ranges::minmax_element(R&& r, Comp comp = {}, Proj proj = {});

Activity

jwakely

jwakely commented on Mar 31, 2022

@jwakely
Member

LWG3180 was applied in e33be08 but was incomplete, as it missed the "and adjust the declarations of std::ranges::minmax_element in 27.8.9 [alg.min.max] to agree" part.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Participants

      @jwakely@philnik777

      Issue actions

        [alg.min.max] hasn't been updated when LWG3180 has been applied · Issue #5375 · cplusplus/draft