Workaround clang bug with basic_string_view
#185
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Clang < 15 has a bug in c++-20 mode where using the
std::basic_string
constructor taking a pointer and size leads to an undefined symbolM_construct
when used with Unicode char types.See llvm/llvm-project#55560
Avoid this by using the range constructor.
Note that when converting this string_view to a std string the bug is triggered again because in
libstdc++
thebasic_string
ctor fromstd::basic_string_view
delegates to the size-range ctor and is instantiated if the source type is convertible tostd::basic_string_view
.This can be verified by commenting out the
std::basic_string_view
conversion operator inboost::core::basic_string_view
Using libc++ also works.