10 Jun
2022
10 Jun
'22
6:17 p.m.
Those are nice and all, but none of them improve the public API or usability of a library.
I second that. C++11 already does a good job at sending the message that we can upgrade again cautiously at some point.
On the other hand features like `std::pmr::memory_resource` or `std::variant` _do_ affect the public API of a library.
I would add std::string_view to this list. Also, pmr is not available on clang, so it's hard to count on it even if moving to C++17. https://godbolt.org/z/11Ez7f64q