You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support for BOOST_BEAST_USE_STD_STRING_VIEW was removed 2 years ago and I don't think that the maintainers of Beast will be willing to reinstate it, so I don't think you can get Beast to use std::string_view like before.
core::string_view does convert to both std::string and std::string_view, so the ambiguity is legitimate. It might be possible to fix; I'll have to think about it.
The easiest fix from your side (which may not be applicable) would be to simply remove the constructor taking std::string const& and rely on the std::string_view constructor for std::string arguments. I don't know if that'll work for you, though; maybe you have legitimate reasons for having the std::string const& constructor (e.g. guaranteed null termination).
(1.84 gcc 13.2)
upgrading boost from 1.75 to 1.84 breaks existing code that boils down to:
https://godbolt.org/z/8TKfP6Pj8
it used to work with
BOOST_BEAST_USE_STD_STRING_VIEW
. how do I get it to usestd::string_view
like before?The text was updated successfully, but these errors were encountered: