P3862 wants to postpone adding subview to string due to some inconsistent behaviors. I think there are alternative approaches: ensuring all functions returning a zstring_view include a "z" in their names (or using "c" for cstring_view). This way, users can clearly distinguish between these overloads. string_view has been around in C++ for many years and is widely used, so developers are already familiar with this kind of distinction. I also suggest applying the same naming convention to zstring_view (or cstring_view), rather than having different overloads of the same function name return inconsistent types.