Is there sense in using const std::string& arguments in C++17?

Question

By getting string_view in C++17 we got cheap method of passing both std::string and char* to functions that do not take ownership of the s

Answer 1

Yes.

The problem with std::string_view is that it doesn't remember if it points to a null-terminated string or not.

If you're writing a wrapper for a C api that uses null-terminated strings, you would have to constantly copy your std::string_views into std::strings to make sure you have null-terminators.