
9 Feb
2018
9 Feb
'18
12:06 a.m.
On 8 February 2018 at 17:58, Peter Dimov via Boost
And, if we're talking about string_view in particular, it's often used in interfaces as a function parameter so it'd be pretty much guaranteed to blow up unless boost::string_view and std::string_view happen to share the same layout.
Again, this was my point from the start, if a standard lib provides a (std-)facility, that's the one that should be used, just to avoid that problem. boost::string_view is just impersonating std::string_view, no guarantee that they are the same, std::string_view should be used, also inside boost (if available). On STL-level, this happens as well of course, between different versions. Thanks, for the clarification... degski