Carbon Language Successor Strategy: From C++ Interop to Memory Safety - Chandler Carruth - CppNow 23

Channel:CppNow · Length:1:38:57 · Published:2023-09-08 · Views:24347

Watch on YouTube

Summary

Chandler Carruth's CppNow 2023 talk describes Carbon as a successor language to C++ rather than a superset, focusing on C++ interop and a path to memory safety in large existing codebases. It explains why Carbon takes a different approach from Cpp2 and Circle.

Why HN recommends it

HN cites it as the authoritative statement of Carbon's memory safety plans, including its borrow-checker-like direction.

Talks like better reflect more recent plans around this topic. — HN, 2024

Programming language design · C, C++, Rust, Go & systems languages

Subtitles (excerpt)

so my name is John mccruth I work at Google uh let me take this offer will you hear me a little better I work at Google I'm one of the I'm the technical lead for Google's software foundations I tend to focus on programming languages and compilers I've worked on clang and Noble VM and C plus plus for a long time but today I'm going to try and talk to you about carbon and uh kind of the the successor strategy we have for carbon uh by the way the slides are live you can go check them out there are a bunch of links in the slides but it's very hard to click links on an actual slide deck so I do encourage you to go and grab them if you want to kind of click on links that I'm mentioning here to remind start off just what kind of folks about carbon cart the carbon language is an experimental successor to C plus plus it's an experiment we're running to see if we can build a compelling successor language for C plus and one of the things that's quite clear is that there's a lot of confusion about what we mean by successor I think a lot of different people have different meanings all I can do is tell you what I am trying to say when I use the term successor for me there are two kind of critical criteria for being

On Hacker News

(Carbon lang dev here.) Carbon is intended to be memory safe! (Not sure whether you intended to write a double negative there.) There are a few reasons that might not be clear: * Carbon has relatively few people working on it. We currently are prioritizing work on the compiler at the moment, and don't yet have the bandwidth to also work on the safety design. * As part of our migration-from-C++ st… — josh11b, 2024-11
>Carbon wants to ship a finished working Carbon language, then bolt on safety (somehow) but, only for some things, not data races for example, so, you still don't actually have Rust's Memory Safety I'm not sure this is correct. As I understand it, Carbon's plan is to add a borrow checker like Rust's. From a recent talk[0][1] by one of the lead developers: >Best candidate for C++ is likely similar… — Vt71fcAqt7, 2024-06
You're right. In fact it was in the previous slide[0] from that same talk. Thanks for pointing that out. [0] [VIDEO] — Vt71fcAqt7, 2024-06
Unless something has chnaged since this talk[0][1], I don't think that is accurate. >Best candidate for C++ is likely similar to Rust’s borrow checker It is stated clearly in the talk that this is true for Carbon as well [0] [LINK] [1] relevant timestamps: [VIDEO] [VIDEO] — Vt71fcAqt7, 2024-03
After the talk, the activity on it is nearly zero since then, in a world where ideas are cheap, show me the code, this does not seem promising to me. On the other hand, carbon has been very actively developed since its announcement, which also claims to be a typescript-for-c++. Now it also wants to be a memory safe: [VIDEO] I'm forced to learn rust but I hope carbon will take off ASAP so I can be… — synergy20, 2023-11

Related videos