Taming the UB Monsters in C++

Re:Taming the UB Monsters in C++ by jcranmer on Monday March 31, 2025 @09:16AM (#43534712)

WG21 is well down the path of actively being hostile to the implementers of C++. There was a recent proposal where all 4 implementers [1] stood up and said "no", and the committee still voted it in, ignoring their feedback.

[1] C++ has only 4 implementations these days, Clang, EDG, GCC, and MSVC; everything keeping up with the standard is a fork of one of these projects.

[ Parent | on HN ]

Re:Taming the UB Monsters in C++ by pjmlp on Monday March 31, 2025 @10:37AM (#43535574)

This is why I see C++26 as the last great standard, it would likely be C++23 if it wasn't for reflection.

Not that WG21 won't produce further ones, just like has happened with other ecosystems of similar age, who cares about Fortran 2023, or COBOL 2023 revisions, despite their critical use in many research projects, or companies infrastructure.

It is already good enough (minus the security issues), for the existing infrastructure that relies on C++, and most of the new stuff isn't helping.

[ Parent | on HN ]

Re:Taming the UB Monsters in C++ by quuxplusone on Monday March 31, 2025 @08:58PM (#43541739)

Which proposal?

[ Parent | on HN ]