🤔 What's the problem you've observed?
The following two lines cause an issue in compilers set to C++17 or higher. Causing a deprecated declaration warning. This warning is ignorable of course. However, it is not ignorable that std::codecvt_utf8 is set to be removed in C++26. So compilers set to C++26 will not be able to built/usage the C++ implementation of cucumber/gherkin
|
std::wstring_convert<std::codecvt_utf8<char32_t>,char32_t> cv; |
|
std::wstring_convert<std::codecvt_utf8<char32_t>,char32_t> cv; |
Reference: https://en.cppreference.com/w/cpp/locale/codecvt_utf8.html
✨ Do you have a proposal for making it better?
I currently don't have sufficient knowledge on the UTF/codecvt part of the library to make a decent proposal
📚 Any additional context?
No response
🤔 What's the problem you've observed?
The following two lines cause an issue in compilers set to C++17 or higher. Causing a deprecated declaration warning. This warning is ignorable of course. However, it is not ignorable that
std::codecvt_utf8is set to be removed in C++26. So compilers set to C++26 will not be able to built/usage the C++ implementation of cucumber/gherkingherkin/cpp/include/gherkin/cucumber/gherkin/utils.hpp
Line 34 in 2cbeea3
gherkin/cpp/include/gherkin/cucumber/gherkin/utils.hpp
Line 45 in 2cbeea3
Reference: https://en.cppreference.com/w/cpp/locale/codecvt_utf8.html
✨ Do you have a proposal for making it better?
I currently don't have sufficient knowledge on the UTF/codecvt part of the library to make a decent proposal
📚 Any additional context?
No response