On 11 Dec 2025 22:44, Vinnie Falco via Boost wrote:
On Sun, Nov 16, 2025 at 6:48 PM Braden Ganetsky via Boost < boost@lists.boost.org> wrote:
...
Now that the release is over with I'd like to get back to this conversation. I believe there is enough smoke / friction here that warrants a resolution. I would like to see:
* Only one string_view in Boost * In a public directory (not detail) * Strong interop with std::string_view
Boost already has enough detractors that we can't afford to push an unergonomic duplicate of a std library component (especially one that is already 8 years old). If the project is going to justify its level of std type duplication then we need to provide added value. The string_view from utility is not ergonomic, while the one in core::detail is.
I think, this discussion will end with nothing, as we had it before. If we want to change the status quo, we need to come to a community decision on what to do. The process we have for this is a review. Specifically, we need a proposal of what to do about boost::string_view and boost::core::string_view, which we need to review and accept or reject it in the end.