C constructs that still don't work in C++ | Hacker News

Hacker News users debated why some C features still don’t map cleanly to C++, despite decades of overlap between the languages.

The discussion pointed to C++’s standards-first design and slower compiler implementation as reasons compatibility gaps persist.

Examples raised included atomics, _Noreturn, inline, anonymous structs, and restrict, which can behave differently or lack direct equivalents in C++.

The thread underscored how partial interoperability still affects code migration, portability, and team decisions between C, C++, and even Rust.