Skip to content
0:00 / 0:00

#rust#borrow-checker#systems-programming

The Rust Programming Language

Google TechTalks

349K subscribers • 67 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Alex Crichton, Rust core team member
  • May be out of date. The tools, versions or practices it shows have likely moved on.

Intermediate. Assumes working knowledge.

98K views11 years ago2 recommendations

Programming languagesSystems programmingRustMemory managementConcurrency and parallelism

Alex Crichton introduces Rust, explaining how its type system guarantees memory and thread safety without a garbage collector.

Google Tech Talk June 6, 2015 (click "show more" for more information) Presented by Alex Crichton ABSTRACT Rust is an exciting new programming language that combines fine-grained control over memory layout and allocation patterns with memory and thread safety. It reached 1.0 in May and is rapidly gaining acceptance in projects including Servo (Mozilla's next generation parallel layout engine), a block store being developed by Dropbox, and numerous startups. Its features include zero-cost abstractions, move semantics, guaranteed memory safety, threads without data races, trait-based generics, pattern matching, type inference, minimal runtime, and efficient C bindings. ‚Alex Crichton will present an introduction to the Rust programming language, explain how it can be used to build performant, reliable systems, and answer your questions. Speaker Info: Alex Crichton ‚About the speaker: Alex Crichton is a member of the Rust core team working at Mozilla Research. He focuses on the standard library, Cargo, crates.io, and Rust's tooling and infrastructure experience. He's been at Mozilla for almost two years and graduated from Carnegie Mellon in 2013 with a BS in both Computer Science and Electrical and Computer Engineering.

Why it's here

2 people recommend this

What people say. Recommended as a classic introduction to Rust's safety guarantees and systems programming capabilities.

Moments people linked to

u/asmx85in r/programming • Recommends

On “"Is Parallel Programming Hard, And, If So, What Can You Do About It?": July 2016 Update”

…ta. If a "new" programmer introduce new functions that work on that data he could easily screw things up. In Rust this cannot happen, because the typesystem does not allow to misuse data in that way, either the data structure is not "ready" to be used in a concurrent fashion or use concurrent "ready" data structures the wrong way. some talks: link to this video link to this video (old thread creation syntax) link to this video…
5View on Reddit

u/Bas1l87in r/rust • Recommends

On “Rust is going through puberty”

Fair enough. I think I have found sufficient evidence. 1. Please see this talk by Alex Crichton: link to this video . He says "Another question that I get a lot is 'Should I be using Rust right now?' and my answer is '*yes!*', i think *everyone shall be using Rust*. Some reasons i will give behind that are..." 2. And this talk (also happened to be by Alex Crichton): link to this video . He says "... zero-cost abstractions. What this basically means is something that at compile-time you can have this very nice interface, it's very easy to use, it's very fluent to use, but it all optimizes away to nothing." I think that's exactly what I was talking about. The first passage implies that Rust is as easy as the ea…
1View on Reddit