On Sun, Dec 14, 2025 at 5:35 PM Peter Dimov via Boost <boost@lists.boost.org> wrote:
Since this problem will eventually go away on its own, I'm not particularly invested in solving it now.
What I do have an opinion about is that core::string_view should be public and documented, because this solves an immediate problem for the library authors who currently use it in their public APIs (and for the users who encounter it).
There are modern libraries like Boost.Json and Boost.URL (and the upcoming Boost.Beast2) that use core::string_view in their public interfaces and will likely continue to support C++11 for a long time. I think making core::string_view public is the least we can do. It does not make sense to reference a type in the docs that is included from boost/core/detail/string_view.hpp.