[range.utility.conv.to] Reuse `container-compatible-range` in `ranges​::​to`?

[hewillk]

[range.utility.conv.to]:

It seems like:

If C does not satisfy input_range or convertible_to<range_reference_t<R>, range_value_t<C>> is true:

can be replaced with:

If C does not satisfy input_range or R satisfy container-compatible-range<range_value_t<C>>:

But it doesn't seem necessary.

[eisenwave]

If we wanted to do this, it seems like we would need to move the definition of container-compatible-range into the library introduction, out of the [container.intro.reqmts].

It's currently only used in [containers], and stated to apply "in the definition of containers".

[hewillk]

If we wanted to do this, it seems like we would need to move the definition of container-compatible-range into the library introduction, out of the [container.intro.reqmts].

It's currently only used in [containers], and stated to apply "in the definition of containers".

Not necessarily. container-compatible-range is also used in [string].

[eisenwave]

Fair point, but std::string is a sequence container, so there is a clear connection to [containers], even though it's still a bit weird not to make it a "global" concept in the library introduction.

[hewillk]

Fair point, but std::string is a sequence container, so there is a clear connection to [containers], even though it's still a bit weird not to make it a "global" concept in the library introduction.

Yes. But I am also highly sure that this condition of ranges::to is specifically intended for the containers in the first place.