Andrey Semashev wrote:
I think, this discussion will end with nothing, as we had it before. If we want to change the status quo, we need to come to a community decision on what to do. The process we have for this is a review.
I don't see what's there to review. core::string_view is more than eligible for being a documented component. It's being used by 8 Boost libraries in their user-facing API. This is exactly what Core was created for. Even if we applied an unreasonably high standard for what needs to go into Core - and we don't - it still clears it. I can see no technical or procedural justification for objecting to core::string_view. At this point, I'm inclined to start to think that objections are malicious in nature. Amusingly, the "official" boost::string_view is only used twice, and one of these is probably a mistake that should be rectified. :-)