Rust for UE ?

[anonymous_user_15fbac48]

@Emaer

First of all there is no C/C++ language. Quick example: VLA is legal in C, but illegal in C++. This is the main reason why C++ is being hatred. Because it is taught as “C with classes.”
Compatibility of C and C++ - Wikipedia
I highly recommend this video: https://youtube.com/watch?v=YnWhqhNdYyk

In modern C++ we have smart pointers and RAII. Using raw pointers (with raw new/delete) is antipattern. UE4 use raw pointers heavily.
In modern C++ we avoid macros because we have type safe constexpr and templates. UE4 uses macros heavily, UObject cannot be templated.
In modern C++ we prefer composition over inheritance and generic programming. UE4 is “inheritance-everywhere”
In modern C++ raw loops can be replaced with range-for or even better with algorithms/std::ranges.
C++20 introduce modules, so headers can gone.

OOP generally isnt bad, its simply misunderstood. Like Alan Key, considered as a father of OOP says:
“I’m sorry that I long ago coined the term “objects” for this topic because it gets many people to focus on the lesser idea. The big idea is messaging.”

As you can see, these are not problems of the language itself, but flaws of UE4 codebase. Introducing a new language will not make them magically disappear.

So, to what extend is modern C++ as safe language? Rust is 100% safe. Well, maybe make it a 99%…

And for the record, since you mentioned how UE4 is written in the first place. WinRT is also written in a object oriented way. It got Win32, so C in it, too. However, unlike C++/WinRT, Rust/WinRT is still 100% safe according to MS no matter what the actual underneath code is. The same with C# for Unity. Unity isn’t written in C#, but C++. Any gameplay code written still will fully or at least mostly draw from the advantages of the language that it was written in.

Any Rust game logic will be safe by default unless written in unsafe code blocks provided that the bindings are also safe and not raw bindings going directly into C++ code via C.