4 ms·
It's probably not too high level for game dev. However, modern AAA game dev is largely about customising and upgrading large existing game engines, which are a
by mike_hearn 11y ago
It's probably not too high level for game dev.
However, modern AAA game dev is largely about customising and upgrading large existing game engines, which are all C++ based. Rust could be used for them, but isn't, and the extra features Rust brings are not compelling enough to rewrite huge amounts of working code and suffer (re)training costs.
This is a hole many new languages find themselves in. JetBrains have come up with a very clever solution for their Java/Scala competitor Kotlin: the language was carefully designed from the ground up with perfect Java interop in mind (Java/Kotlin call into each other seamlessly, the IDE can refactor across languages, Kotlin uses the same standard library etc). And quite amazingly, the IDE can automatically rewrite Java into Kotlin. This isn't a party trick, it works very well.
I think if Rust wants/wanted to be a serious competitor to or upgrade path from C++ it'd have needed to take at least some level of C++ interop into account from the start such that Rust and C++ could be intermixed freely. AFAIK though, the best you get is a typical C export/import layer which is too trivial to be compelling.
Of course, it's a lot harder than connecting with Java because of the way C++ stuff is defined using header files. But at least basic interop could have been done.
- steveklabnik 11y agoYes, this is a good point about AAA. The issue with interop is on the C++ side, unfortunately, not our side. Until C++ has a well-defined ABI, it's not really possible.
- mike_hearn 11y agoC++ has a well defined ABI on many important platforms. On GCC/LLVM based platforms it's standardised in specification documents. On Windows, I think the Visual C++ ABI is the de-facto standard. Regardless, there are only a handful of top C++ compilers. Interop with even one of them would be of tremendous value.
- steveklabnik 11y agoYeah, I mean, the basics of interop might be possible, it will just never be as robust as it could be if C++ had features better designed to play with other languages. (This of course also affects Rust as well; we don't have a defined ABI either.)
- mike_hearn 11y agoSure, you can't get completely perfect interop. However a LOT of real C++ codebases don't use or explicitly ban some of the trickiest features, so even partial support can go a long way. For instance, supporting the basic class/vtable layout C++ uses (or even just adopting the C++ ABI for Rust itself here) along with char* strings, would immediately allow you to call into a lot of real C++ APIs, albeit older ones. Supporting C++ value types, even without templates, would in turn be enough to support quite a lot more. For instance Unreal Engine defines its own string types, as do Qt and so on.
- steveklabnik 11y agoYeah, to be clear, I think such a thing would have value too. Just hard to get 100%, there are always gonna be caveats.
- pcwalton 11y agoI totally agree. As I mentioned in a sibling comment, maybe the right solution is for Swift and Rust to solve the problem together by using libclang in the same way. To be concrete, I could envision some sort of bolt-on "inline C++" feature that libclang would expose to all LLVM-based languages. It wouldn't have to be principled interop any more than Objective-C++ is principled interop. It'd just need to get the job done.
- pcwalton 11y agoIt's not clear to me that it's impossible. The ABI isn't a huge issue; templates are, though. I can see a potential path forward by using clang heavily, but it requires a lot of thought. Isn't Swift looking heavily into C++ interop? It might make sense to collaborate with them to get it to work in both languages.
- steveklabnik 11y agoSwift is implemented in C++, and uses LLVM stuff that we don't because it's not exposed in the C ABI, last I heard.
- pcwalton 11y agoWell, sure, but how the compiler calls into libclang/LLVM isn't the difficult issue here. The more interesting issue is how, conceptually, the Swift or Rust compiler would use libclang to interoperate with C++ in a foreign environment. Once that's established, writing C bindings to whatever part of libclang is necessary should be straightforward.
- fiedzia 11y agoIf you want to be fully compatible with C++, you have to be fully compatible with all its issues and design mistakes. If those could be fixed without sacrificing compatibility, they would be fixed within C++ already. In case of rust, such compatibility would defeat the purpose of its existence.