On Sun, Dec 14, 2025 at 12:39 PM Andrey Semashev via Boost <boost@lists.boost.org> wrote:
I already said what I think should be done. Make a proposal to keep just one string_view in Boost. Whether that is core::string_view or boost::string_view.
Considering that most codebases use C++17 or newer, and that boost::string_view is neither constructible from nor convertible to std::string_view, using it in a public API of a library is effectively as good as using: namespace mylib { struct string_view { const char *ptr; std::size_t len; }; } // namespace mylib I suspect very few users actually use this type, if any. We can likely leverage that. We could promote core::string_view to the boost namespace and use boost/string_view.hpp as the include path. I would be happy to write a proposal if no one is going to volunteer. Thanks