I use core::string_view in Boost.MySQL, too, because implicit conversion
to
std::string_view is super important for me. core::string_view has std::format support, too. Not having any of these would have forced me to upgrade to C++17 already. So I'd like to see core::string_view as a public type, as it's already widely used in our interfaces.
Why don't we have a string_view in boost.compat? if we had a compat:;string_view that is identical to the C++17 implementation. We then have one standard with two implementations and not three slightly different string_views.
Once compat adds this the consuming libraries (e.g. boost.mysql or boost.url) can use compat and the other implementations just become a relic that isn't used within boost anymore.
The same would probably apply to core/span.
This could be a good way to implement the "make it public" proposal. I already use Boost.Compat in MySQL, so I'd be happy to see string_view there. One thing to note is that boost::core::string_view does not support the Traits template parameter that boost::string_view and std::string_view do. I personally don't need this at all, but I don't know if that's true for the other libraries.
_______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/YJQLWHLW...