Skip to content
0:00 / 0:00

#ownership#rust#aaronturon

Keynote - Rust: confident, productive systems programming by Aaron Turon

Scala Days Conferences

10K subscribers • 22 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Presented by Aaron Turon, Rust core team member

Beginner. No background in the topic needed.

13K views9 years ago1 recommendation

Programming languagesSystems programmingRustConcurrency and parallelismMemory management

Aaron Turon explains Rust's core concept of ownership and how it guarantees memory and thread safety without a garbage collector.

This video was recorded at Scala Days Chicago 2017 Follow us on Twitter @ScalaDays or visit our website for more information scaladays.org Abstract: Rust is a language with a new vision of systems programming. It gives you low-level control and predictability but also provides the safety and ergonomics of languages like Scala. The secret sauce is Rust's core notion of "ownership", which enables: - Memory safety without garbage collection. - Concurrency without data races. - Abstraction without overhead. In this talk, I'll explain ownership and show how Rust uses it to guarantee thread safety, amongst other things. I'll say a bit about integrating Rust code with other languages. And I'll also cover some of the lessons the Rust community has learned in how to do open, consensus-driven language evolution, so that we also achieve: - Stability without stagnation.

Why it's here

1 person recommends this

What people say. Recommended as an excellent explanation of Rust's ownership model.

Moments people linked to

u/neutralinostaritertools · rustin r/rust • Recommends

On “A great SO answer about std::cell”

Very nice, and it's important for rust to have good explanations for its core concepts. I'm a big fan of the ownership explanation that aturon has given in talks a few times. (~~I am on mobile, so no link handy~~ I'm really handy with links actually: **aturon on ownership**) A nitpick is that Cell uses no runtime checking at all, it changes aliasing information given to the compiler and disallows references to the interior (=no aliasing *except the aliasing with `Cell` around it*), at compile time.
24View on Reddit