Considering what would happen if Rust came bundled with a C/C++ (cross)-compiler. It'd certainly be convenient, but having the Rust project be on the hook for C++ compiler bugs sounds pretty awful...
Conversation
Replying to
What I really want is this, but for Rust
Quote Tweet
Replying to @bascule @rikarends and 2 others
D recently added an "ImportC" feature like this.
The implementation was only 4klocs, which is pretty cool:
github.com/dlang/dmd/pull
1
5
Replying to
Problem is, it looks from a glance like it's just C, not C++/Obj-C/COM. Which isn't very useful these days :(
1
4
Replying to
C would be really helpful for FFI bindings to C libraries.
Just an anecdote, but that's like 99% of what I care about in terms of what I personally develop. I've used bindgen's C++ support like once.
3
8
Android is using the usual shared toolchain, build system and build sandbox for heavily integrating Rust into the OS. It's not using Cargo and it's heavily using multiple forms of interoperability with C++ due to that being the prior basis for most stuff.
2
1
It also gets a lot of Java/Kotlin interoperability from the integration into the build system, HIDL, etc. although it's not the focus of the post. It has to fit into an existing world largely consisting of Java and also lots of C++ at the lower levels where Rust will be used.

