On 4 Nov 2025 19:05, Klemens Morgenstern via Boost wrote:
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.
If my counting is right, we'd have three, plus std::string_view. As if two weren't enough. BTW, the version in Boost.Compat wouldn't have a conversion operator to/from std::string_view because one doesn't exist in std::string_view and Boost.Compat implements standard components verbatim.
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.