C++11

[LoganDark]

Will the C++11 version be maintained any longer? Or are you deprecating it forever in favor of the newer standard?

[ColinH]

We are concentrating all efforts on the C++17 "version", the C++11 version is not deprecated, it's gone because it never really existed outside of betas and development versions: we made the switch to C++17 before releasing a version 1.0.0.

We will not continue with C++11, but if you are using a snapshot of taocpp/json with C++11 and can't upgrade to C++17 you can still ask questions and we will give "unofficial" support or help you back-port features where necessary and possible.

[LoganDark]

I'm a bit disappointed you decided to ditch C++11 at the last moment, because this library had the best performance of any JSON library, and it just so happens that C++11 is the most common version of C++ (that I'm aware of).

[ColinH]

Thanks for the praise! And sorry for the bother, there were simply too many simplifications and enhancements to the code made possible by using the newer standard, we couldn't resist any longer...

[d-frey]

...and by "couldn't resist" we also mean that we previously had to maintain backported versions of std::optional and std::string_view, which were not 100% compatible with the actual standardized version (as std::string_view also requires modifications to std::string, constexpr could not be used fully with C++11, etc.). It wasn't a light-hearted decision, it was more-or-less necessary and frees up more resources on our side.

[brlcad]

Ditto disappointment. It knocks this outstanding implementation out of contention for our software stack, at least until 17 is reliably implemented and available everywhere, all platforms. :(