[boost] Re: utility::string_view and core::detail::string_view

On 12/11/25 20: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
As I understand it, this is a political problem.
   - boost::string_view has already been accepted into Boost.
   - Community consensus is overwhelmingly that it should interop better 
with std::string_view, but its maintainer doesn't want to make that change.
   - There is no process for forcing the maintainer to make that change.
   - There is no process for forcibly replacing the maintainer.
   - There is no process for removing the library from Boost and 
replacing it with another string_view library.

Once a library passes its review and is accepted, it remains a part of 
Boost forever while still being under the control of its original 
author.  If a problem comes up after review, the option is to politely 
the library's maintainer to please fix the problem.


-- 
Rainer Deyke - rainerd@eldwood.com