Using ```estring_view``` instead of ```std::string_view``` for APIs, to avoid ABI inconsistency between C++ versions

Question

Using ```estring_view``` instead of ```std::string_view``` for APIs, to avoid ABI inconsistency between C++ versions

lihuiba opened this issue 8 months ago · comments

We make extensive use of string_view for efficient handling of strings. And we use it in C++14 mode by cheating std library, and let it think we are in c++17 mode. This compiles OK, but leads to ABI inconsistency in binaries.