Google Launches Carbon, an Experimental Replacement for C++

Post by Razengan » Wed, Jul 27, 2022, 9:54 AM UTC

layer8 wrote: post #200

Terretta wrote: post #66

How to make your replacement for a C language Google-able: name it after an API for a C language: Carbon was one of two primary C-based application programming interfaces (APIs) developed by Apple for the macOS (formerly Mac OS X and OS X) operating system. Compare also keywords or key terms: Carbon will be built on a foundation on modern programming principles, including a generics system, that would remove the need…

Since “C++” reads like a Carbon ion with two positive charges, they could have called it “Cation”.

Post by est31 » Thu, Jul 28, 2022, 2:49 PM UTC

mleonhard wrote: post #240

est31 wrote: post #55

Earlier quoted context omitted.

> In Rust, moves are destructive (which simplifies implementions - you don't need an "empty" state) and always bitwise (which is usually fine, so long as they're destructive); and copies are always explicit so you don't have the above problem. Rust has implicit copies too, e.g. if you do: let v = 2u16; foo(v); then v is being copied. What Rust does not have is implicit deep copies. The auto-copying depends on the typ…

In Rust, types implement the Copy trait and the Drop (destructor) trait independently. Vec could easily implement Copy. It doesn't because copying a Vec requires an expensive heap allocation, which can surprise users when it happens implicitly.

    struct Foo;
    
    impl Copy for Foo {}
    impl Drop for Foo {
        fn drop(&mut self) {
            // ...
        }
    }

    error[E0184]: the trait `Copy` may not be implemented for this type; the type has a destructor
     --> src/main.rs:3:1
      |
    3 | impl Copy for Foo {}
      | ^^^^^^^^^^^^^^^^^^^^ `Copy` not allowed on types with destructors