Re:Std::visit is everything wrong with modern C++ (2017)
by Torkel on Saturday December 05, 2020 @11:04AM
(#25315500)
Modern C++ isn’t all that portable either.
[ Parent
| on HN ]
Re:Std::visit is everything wrong with modern C++ (2017)
by FartyMcFarter on Saturday December 05, 2020 @11:10AM
(#25315554)
IMHO the last big upgrade to C++ was C++11, which is supported by lots of toolchains. It added move semantics, decent smart pointers, and a crapload of other improvements.
C++14 and C++17 were minor upgrades by comparison, so I'd say C++11 can rightly be called modern C++, though others may disagree.
Re:Std::visit is everything wrong with modern C++ (2017)
by ncmncm on Saturday December 05, 2020 @12:54PM
(#25316599)
I see that you are wholly unaware of C++20, which (combined with '14 and '17) is as large a step from C++11 as C++11 was from C++98.
Re:Std::visit is everything wrong with modern C++ (2017)
by FartyMcFarter on Saturday December 05, 2020 @01:13PM
(#25316785)
C++20 is barely out yet, and not supported by any toolchain. If that's the only version that counts as modern C++, then I agree that modern C++ isn't portable :)
Re:Std::visit is everything wrong with modern C++ (2017)
by jcelerier on Saturday December 05, 2020 @11:46AM
(#25315879)
c'mon, you can run C++17 code on Commodore 64 (https://www.youtube.com/watch?v=zBkNBP00wJE) and MS-DOS (https://www.youtube.com/watch?v=yHrC_rZUaiA), what more do you want ?