Proposed resolution:

This wording is relative to n4917.

1. Modify [iterator.synopsis], header <iterator> synopsis, as indicated:

   #include <compare>              // see [compare.syn]
   #include <concepts>             // see [concepts.syn]
   
   namespace std {
     […]
     
     // [const.iterators], constant iterators and sentinels
     // [const.iterators.alias], alias templates
     […]
     template<input_iterator I>
       using const_iterator = see below;                                               // freestanding
     template<semiregularclass S>
       using const_sentinel = see below;                                               // freestanding
   
     […]
     template<input_iterator I>
       constexpr const_iterator<I> make_const_iterator(I it) { return it; }            // freestanding
   
     template<semiregularclass S>
       constexpr const_sentinel<S> make_const_sentinel(S s) { return s; }              // freestanding
     […]
   }
   

2. Modify [const.iterators.alias] as indicated:

   template<semiregularclass S>
     using const_sentinel = see below;
   

   -2- Result: If S models input_iterator, const_iterator<S>. Otherwise, S.

[ 2022-11-12 Approved at November 2022 meeting in Kona. Status changed: Voting → WP. ]

[ 2022-09-23; Reflector poll ]

Set status to Tentatively Ready after six votes in favour during reflector poll.

The current standard does not have any constraints on const_sentinel template parameters, which makes it possible to pass almost any type of object to make_const_sentinel. It would be more appropriate to constrain the type to meet the minimum requirements of the sentinel type such as semiregular as move_sentinel does.