3 ms·

> Rust had to be dragged kicking and screaming into integration with other languages Rust has integration with the C ABI(s) from day 1, which makes sense becau

> Rust had to be dragged kicking and screaming into integration with other languages Rust has integration with the C ABI(s) from day 1, which makes sense because the C ABI(s) are effectively the universal ABI(s). > and its C++ compatibility is a joke I'm not sure why you would want Rust to support interoperability with C++ though, they are very different languages. Moreover why does this fall on Rust? C++ has yet to support integration with Rust! > compared to Swift Swift bundled a whole C++ compiler (Clang) to make it work, that's a complete deal breaker for many. > Rust historically has been hostile to anything besides unsafe C ABI FFI Rust historically has been hostile to making the Rust ABI stable, but not to introducing other optional ABIs. Introducing e.g. a C++ ABI has just not been done because there's no mapping for many features like inheritance, move constructors, etc etc. Ultimately the problem is that most ABIs are either so simple that they're the same as the C ABI or they carry so many features that it's not possible to map them onto a different language.

maxk42 2y ago
I would like to point out also that C++ is not yet compatible with itself. Even GCC has dozens of C++ features it doesn't implement and it was the first compiler to implement 100% of C++11: https://gcc.gnu.org/projects/cxx-status.html https://gcc.gnu.org/projects/cxx-status.html
- bluGill 2y ago
  Technically true but in the real world those are rare edge cases.
  - maxk42 2y ago
    Only because they're not used. If you're not going to implement the spec then is it really a spec?
    - SkiFire13 2y ago
      It could also be argued that they aren't used because not all major compilers implement them.
      - bluGill 2y ago
        If there was demand major compilers would implement them. That is why despite being difficult all major compilers are working on getting modules working.
bluGill 2y ago
I have millions of lines of c++. I'd love t use something else but without interoperability it is much harder. If you only write C you are fine. If you write java you want java interoperability, similear for lisp, or whatever your existing code is in.

maxk42 2y ago

I would like to point out also that C++ is not yet compatible with itself. Even GCC has dozens of C++ features it doesn't implement and it was the first compiler to implement 100% of C++11: https://gcc.gnu.org/projects/cxx-status.html https://gcc.gnu.org/projects/cxx-status.html

bluGill 2y ago
Technically true but in the real world those are rare edge cases.
- maxk42 2y ago
  Only because they're not used. If you're not going to implement the spec then is it really a spec?
  - SkiFire13 2y ago
    It could also be argued that they aren't used because not all major compilers implement them.
    - bluGill 2y ago
      If there was demand major compilers would implement them. That is why despite being difficult all major compilers are working on getting modules working.

bluGill 2y ago

I have millions of lines of c++. I'd love t use something else but without interoperability it is much harder. If you only write C you are fine. If you write java you want java interoperability, similear for lisp, or whatever your existing code is in.