News for hackers. Stuff that matters.
Re:We used C++20 to eliminate a class of runtime bugs by superkuh on Friday January 14, 2022 @04:21PM (#29940613)
C++?? every 3 years isn't nearly as bad as say, the Rust situation, but it does mean that a linux desktop distro compiler can only compile stuff from "hip" devs writing in C++ for about 3 years after the distro release. It means if you chose to use these language features the vast majority of people will not actually be able to compile it.

So balance that. If you're not just distributing binaries, if you have geek end users compiling, maybe don't always use the latest bleeding edge C++?? features.

Re:We used C++20 to eliminate a class of runtime bugs by jcelerier on Saturday January 15, 2022 @03:13AM (#29944726)
Nah, this is also why the Linux desktop is behind. On Windows I build on win10 VMs with the very latest C++20 features and can ship back to Win7 because Windows does not idiotically tie a compiler version to an operating system.
Re:We used C++20 to eliminate a class of runtime bugs by superkuh on Monday January 17, 2022 @10:39AM (#29967620)
If you have to use a VM to compile instead of doing it on your OS you've lost the game too. It is a cross-OS problem with almost all modern software.
Re:We used C++20 to eliminate a class of runtime bugs by pjmlp on Saturday January 15, 2022 @04:01AM (#29944964)
I am quite curious when clang will catch up with C++20 (GCC is much better).

Meanwhile I am enjoying modules in VS 2022, even if there are some hiccups.