Proposed resolution:

This wording is relative to N4958.

1. Modify [range.utility.conv.adaptors] as indicated:

   template<class C, class... Args> requires (!view<C>)
     constexpr auto to(Args&&... args);
   template<template<class...> class C, class... Args>
     constexpr auto to(Args&&... args);
   

   -1- Mandates: For the first overload, C is a cv-unqualified class type.

   -2- Returns: A range adaptor closure object ([range.adaptor.object]) f that is a perfect forwarding call wrapper ([func.require]) with the following properties:

   1. (2.1) — It has no target object.

   2. (2.2) — Its bound argument entities bound_args consist of objects of types decay_t<Args>... direct-non-list-initialized with std::forward<Args>(args)..., respectively.

   3. (2.3) — Its call pattern is to<C>(r, bound_args...), where r is the argument used in a function call expression of f.

   -?- Remarks: The expression to(args...) is well-formed if and only if the initialization of the bound argument entities of the result, as specified above, are all well-formed.

[ 2023-09-28; Hewill provides alternative wording ]

The new wording form is consistent with the current wording, that is, it has a similar structure with [range.adaptor.object] p1 and [range.adaptor.object] p8.

[ 2023-11-03; Reflector poll ]

Set priority to 3 after reflector poll. Votes split between NAD and using Mandates instead of constraints.

The ranges::to adaptor returns a range adaptor closure object that stores a copy of the decayed parameter pack.

However, the function signature does not constrain the type of arguments, which leads to hard errors within the function body when they cannot be copied (demo):

#include <ranges>
#include <vector>

struct NonMovable {
  NonMovable() = default;
  NonMovable(NonMovable&&) = delete;
};

int main() {
  auto r = std::ranges::to<std::vector>(NonMovable{}); // hard error in MSVC-STL and libc++
}