P3862 points out that basic_string::subview should consider returning cstring_view instead of string_view. I think that concern is reasonable, but I would like to propose my own solution. I believe basic_string should provide two member functions: one returning string_view and another returning z/cstring_view. Under this premise, the proposal should use the name zstring_view rather than cstring_view. The reason is that names like csubview or subcview could be confused with the c in cbegin. In contrast, zsubview or subzview avoids this issue because z is one of the least common letters, so it is unlikely to block future extensions.
P3862 points out that
basic_string::subviewshould consider returningcstring_viewinstead ofstring_view. I think that concern is reasonable, but I would like to propose my own solution. I believebasic_stringshould provide two member functions: one returningstring_viewand another returningz/cstring_view. Under this premise, the proposal should use the namezstring_viewrather thancstring_view. The reason is that names likecsubvieworsubcviewcould be confused with thecincbegin. In contrast,zsubvieworsubzviewavoids this issue becausezis one of the least common letters, so it is unlikely to block future extensions.