Introducing a Memory-Safe Successor Language in Large C++ Code Bases - John McCall - CppNow 2023

Channel:CppNow · Length:1:22:20 · Published:2023-09-06 · Views:18492

Watch on YouTube

Summary

John McCall of Apple's Swift team presents at CppNow 2023 on introducing a memory-safe successor language into large C++ code bases. He argues incremental improvement of C++ hits hard limits and explains Swift's C++ interoperability for gradual migration.

Why HN recommends it

Used as the primary source for Apple's stated plan to make Swift its successor to C++ and for how interop supports gradual transition.

Finaly a recent gem from CppNow 2023 — HN, 2023

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

Subtitles (excerpt)

uh hi my name is Sean McCall and I'm going to be talking to you about uh introducing a memory safe successor language into large code bases uh unless is the agenda let's start by talking about the Apple ecosystem and the languages that we've historically used and where we see Swift fitting into that I'm going to talk about why we think it's so important to use a successful language the ways in which Swifts language designs specifically meet our goals but those should be fairly generalizable to other languages and then I'll talk about ways in which Swift makes it easy to migrate incrementally to it um I want to start though by introducing myself I'm new to this particular slice of the community I've started at Apple in 2008 and joined the clang Project A year later so this is I think my first commit which is adding checks to see whether main returns end so that's the state of crane in 2009 and that's where I started I helped bring up C plus plus in clang um so this is yet another fix to uh name lookup there's about a million of these but I wrote a lot of them uh eventually I became a code owner of prang's lvm ir generation and still M I still do a lot of code review on playing uh here I am just wildly breaking the ABI because we thought it was a

On Hacker News

I'm not a (direct) user of the C++ interop, but everything I've heard about it has been quite positive. A few hopefully relevant resources, first a couple of videos: - "Introducing a Memory-Safe Successor Language in Large C++ Code Bases" (John McCall; CppNow 2023) [VIDEO] - "Swift as C++ Successor in FoundationDB" (Konrad Malawski; Strange Loop 2023) [LINK] And then a series of blog posts by Dou… — glhaynes, 2024-06
I wonder what the author thinks about Swift’s new C++ interop story? Since the Swift compiler includes Clang, and can thus compile both your C++ and Swift into LLVM IR, without the need for an FFI later between the two, couldn’t this be the “Typescript for C++” that the author points out a space for? The Swift folks are very much thinking about Swift as a C++ successor that can be incrementally m… — mannuch, 2023-12
Java also compiles to native code on Android. Try to write an iOS application using only C and C++, instead of either Objective-C or Swift. "Swift was designed from the outset to be safer than C-based languages, and eliminates entire classes of unsafe code" -- [LINK] "Swift is a successor to the C, C++, and Objective-C languages. It includes low-level primitives such as types, flow control, and o… — pjmlp, 2023-09
On the same note, watch Apple's talk at CppCon 2023, "Introducing a Memory-Safe Successor Language in Large C++ Code Bases" [VIDEO] — pjmlp, 2023-09
Yes, Apple themselves, apparently folks wanting Apple to use Rust don't read Apple's documentation or watch talks done by Apple compiler developers. > Swift was designed from the outset to be safer than C-based languages, and eliminates entire classes of unsafe code. -- [LINK] > Swift is a successor to the C, C++, and Objective-C languages. It includes low-level primitives such as types, flow con… — pjmlp, 2025-04

Related videos