>>105662206
It's certainly an oversight but I don't think this is a problem that happens all that often. The main goal of adding string_view was to have an efficient and standardized way of passing strings as references, because some people used const std::string& while others stuck to using const char *. It's not a drop-in replacement for either of those, because it's non-owning unlike a string and not null-terminated unlike a const char *. It has a pretty specific use-case. Also string_view works with all the iterator and range functions, I'm sure you could write a std::ranges one liner which does this.