• onlinepersona
    link
    fedilink
    arrow-up
    1
    arrow-down
    3
    ·
    edit-2
    1 day ago

    I bet this won’t have an impact on memory safety and interop means C++ compilers have to be stricter about memory layout and reduce unspecified edge cases.

    Anti Commercial-AI license

    • robinm@fosstodon.org
      link
      fedilink
      arrow-up
      1
      ·
      1 day ago

      @onlinepersona @snaggen Indirectly it can. Recent studies showed that old code is very unlikely to have security issue. This means that if all new code can be in Rust, while keeping the old code in C++ will be much more secure that rewrite all C++ (because by definition rewrite have more bugs since its new code). So interoperability is both safer and cheaper.

      • 5C5C5C
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        19 hours ago

        It makes total sense that new C++ will contain a higher percentage of bugs than old C++, but after being an almost full time Rust dev for the last two years, you will not convince me that new Rust code has more bugs than old C++ code.

        So far I have yet to come across a bug in any of my Rust code that made it into production. All issue reports from users are still related to the C++ code base that we haven’t managed to fully divorce from.

        The only advantage to C++ interop is that managers want to see new code get deployed immediately and continuously. They don’t want to wait until the corporation’s billions (literally) of lines of code are all rewritten in a new language before they start to see the benefits of that transition.