Rust Concurrency with Alex Crichton
Software Engineering Daily,
Originally posted on Software Engineering Daily
Rust is a systems level language that is built to prevent crashes and eliminate data races. A language like C++ gives you high speed and lots of control, but it is easy to have segfaults, data races, and other problems if you aren’t careful. On this spectrum of control versus safety, we can plot other languages like Java, Go, and Haskell–but none of these languages have the unique feature set of Rust.
Rust’s concurrency model is built on the foundation of ownership–a piece of data can only be owned by a single thing at a time. In today’s interview, Alex Crichton explains ownership, and the other abstractions that give Rust its unique model of concurrency.
|Indeed Prime simplifies your job search and helps you land that ideal software engineering position. The average software developer gets 5 employer contacts and an average salary offer of $125,000. Indeed Prime is 100% free for candidates – no strings attached. And when you’re hired, Indeed Prime gives you a $5,000 bonus if you signed up with the URL indeed.com/sedaily|
|SnapCI is a continuous integration tool built by Thoughtworks. Go to snap.ci/softwareengineeringdaily to check it out.|
|Build apps that communicate with everyone in the world. Voice & Video, Messaging, and Authentication APIs for every application. Start your Free Trial today and get an additional $10 credit account with account upgrade. Learn more at go.twilio.com/podcast|