11 Dec
2025
11 Dec
'25
7:44 p.m.
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. Thanks