Rainer Deyke wrote:
On 12/13/25 16:46, Vinnie Falco via Boost wrote:
On Sat, Dec 13, 2025 at 7:06 AM Rainer Deyke via Boost < boost@lists.boost.org> wrote:
This, on the other hand, does not seem to be the case. I get compile errors if I remove either the std::string_view or the boost::core::string_view overloads.
Could you please create a small reproducing example on https://godbolt.org ?
Thanks. Unfortunately there's nothing we can do to enable this on the core::string_view side. It's fixable by changing the my_class constructor to a template like this: https://godbolt.org/z/bK84j3q39 which incidentally gives you support for `char const*` and `std::string` for free (and for boost::string_view should anyone still need it.) To avoid mentioning core::string_view in your own code, you can do the same except with std::string_view: https://godbolt.org/z/YGT3sYssW This no longer supports boost::string_view, but that's acceptable. Ultimately though, the only thing that will "fix" all these issues once and for all is moving to a C++17 baseline in the Boost libraries that suffer from them, and migrating to std::string_view. The time might be coming. C++17 is the default on GCC 11 and later, and Ubuntu 22.04 has GCC 11 as the system compiler. We just need 20.04 to die (it's already EOL I think?) and figure out the situation on macOS. We'll lose msvc-14.0 though.