News for hackers. Stuff that matters.
Re:Cpp2Rust: Translates C++ to safe Rust automatically by crnakfls on Friday July 10, 2026 @05:48PM (#48865753)
> Notable unsupported constructs include: union, volatile, goto, exceptions, bitfields, placement new, user-defined copy/move constructors, dynamic_cast, const_cast, base classes with fields or non-virtual methods, multiple inheritance, and multi-threaded code.
Re:Cpp2Rust: Translates C++ to safe Rust automatically by antiframe on Friday July 10, 2026 @05:58PM (#48865845)
So, most C++ code I have seen in my forty years of coding.
Re:Cpp2Rust: Translates C++ to safe Rust automatically by bitwizeshift on Friday July 10, 2026 @06:02PM (#48865875)
Lol, “user defined copy/move constructors” That’s actually so many types that would define this
Re:Cpp2Rust: Translates C++ to safe Rust automatically by ahartmetz on Saturday July 11, 2026 @05:45AM (#48870432)
Base classes with fields or non-virtual methods are not exactly rare neither.
Re:Cpp2Rust: Translates C++ to safe Rust automatically by pjmlp on Saturday July 11, 2026 @05:39AM (#48870397)
From the point of view of C++26, which is already ratified, and half implemented in GCC 16, I think your list should even be longer.

The readme is rather slim on C++ versions.