Skip to content
Hallway
0:00 / 0:00

#rust#typesafety#fuchsia

Joshua Liebow-Feeser: "Safety in an Unsafe World" | RustConf 2024

Rust Foundation

7.3K subscribers • 2 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Joshua Liebow-Feeser, Software Engineer at Google

Advanced. Deep dive for people who know the field.

4.9K views1 year ago2 recommendations

Programming languagesSecurityRustLanguage design and type systemsWeb and application security

Joshua Liebow-Feeser explores how Rust's type system can enforce arbitrary safety properties beyond memory safety.

A talk by Joshua Liebow-Feeser (Software Engineer, Fuchsia Security, Google) at RustConf 2024 in Montreal, Canada & online on September 12. Hosted by the Rust Foundation. Abstract: Rust doesn’t just support memory safety, it supports “X-safety”: The ability to teach Rust about arbitrary safety properties, only permitting X-safe code to compile. This talk will explore how this technique has been used to defend against everything from network protocol bugs to cryptographic vulnerabilities, demonstrate novel results based on Joshua’s research, and argue that if we take this aspect of Rust seriously, we can fundamentally reshape how software is written in safety-critical environments. ABOUT RUSTCONF RustConf is a long-running event dedicated to inspiring conversations about the Rust programming language and its community. 2024 sponsors included Devolutions, Google, and others. Thank you to the Rust community for making this year's event so memorable! rustconf.com | rustfoundation.org

Why it's here

2 people recommend this

What people say. Recommended as an excellent demonstration of using Rust's type system to enforce complex safety invariants.

u/SV-97in r/embedded • Recommends

On “Rust in Production: Volvo Ships Memory-Safe ECUs in Production Cars”

>Is the main reason for people pushing Rust in embedded systems due to it's memory safety? It's also a very nice, productive language to use with superb (sane) tooling and sensible defaults. >If you can't properly manage memory in C++ or C wouldn't it be better to improve rather than looking for a language to handle your issues? Why do you think it would be better to just "improve" (which evidently doesn't work if the last decades are anything to go by) and stick with C or C++ when switching languages immediately solves those (and other) issues entirely? >This might be out of ignorance but it feels like this just leads to more software developers lacking low-level knowledge. First of…
10View on Reddit

u/tobegain r/ProgrammingLanguages • Recommends

On “Languages that enforce a "direction" that pointers can have at the language level to ensure an absence of cycles?”

Here is a talk where they use the type system for some awesome things, e.g. to ensure locking order [video
2View on Reddit