A reminder that small details at declaration can have large impacts on memory layouts.

Or why this kind of question never have an absolute answer.

If you forgot that the memory allocator can matter greatly depending on your workload.

This could be a big improvement for C. We'll see how far this goes.

Interesting reasons to let go of Rust, some spaces indeed can have a safety vs performance tradeoff which would justify using good old C.

A harsh reminder that getenv is not thread safe...

Improved static analysis for C straight from GCC. This is definitely welcome.

Indeed, the story of integrating C and C++ with Rust isn't a simple one right now. It might introduce larger attack surfaces. Some improvements are proposed in this paper.

Indeed, the times when we could pretend one was a superset of the other are long gone.

There are really many initiatives to make C and C++ safer lately. I wonder which one will see adoption and what will make its way to the standards.

This is a very concerning for C... and it drifts apart from C++ further. The old "C as a subset of C++" position is less and less valid. Very unfortunate.

Interesting approach. There's still a lot we can achieve with static analysis in those good old languages.

Excellent conclusion to the recent turmoil around undefined behaviors. The way they are currently used as definitely a problem, they shouldn't be ignored in your code (although that's admittedly not that easy). There's hopefully a path forward.

Undefined behavior do exist and well... they're really undefined, don't make any assumption about them.

Nice new feature coming to C. This is useful stuff. It required quite some fighting to get in though.