Henri Sivonen:
> AFAICT, in general a Range
> erases information about whether the storage is contigous. It seems
> complicated to have an interface that seemingly erases this information and
> then behind the scenes tries to re-discover that the Range is actually
> contiguous. It seems to me that this makes it less obvious to the user what
> the performance characteristics are.

You can always have a hidden overload taking std::ranges::contiguous_range.