![New Rustacean artwork](https://is5-ssl.mzstatic.com/image/thumb/Podcasts123/v4/4b/03/b2/4b03b277-686e-92ec-1818-dcea61b72f4f/mza_388948490372677342.png/100x100bb.jpg)
e002: Something borrowed, something… moved?
New Rustacean
English - October 12, 2015 02:24 - 17 minutes - 8.68 MB - ★★★★★ - 79 ratingsTechnology News Tech News rust programming programming languages software Homepage Download Apple Podcasts Google Podcasts Overcast Castro Pocket Casts RSS feed
Something borrowed, something… moved?
Subject: The struct data type constructor, and the basics of Rust’s “ownership” concept and “borrowing” and “moving”.
Follow/Support
New Rustacean:
Twitter: @newrustacean
App.net: @newrustacean
Patreon
Email: [email protected]
Chris Krycho
Twitter: @chriskrycho
App.net: @chriskrycho
Notes
Today’s episode discusses, and the associated source code demonstrates, a few basic behaviors of structs… including borrowing!
After taking a short look at one of Rust’s basic approaches to creating new types, we dive into a fairly thorough overview of how borrowing works in fairly run-of-the-mill Rust code. This is a basic introduction, and as such I’m not getting into things like heap-allocated memory (Box) or dealing with move semantics with threads or closures. (I haven’t actually figured those out well enough yet to write something like this for them!)
As usual, you’ll want to have the src open to see what I’m doing with the components documented below.
Links
rustfmt – a tool for formatting Rust code
repo
“rustfmt-ing Rust`
Reddit discussion
RFC for incremental compilation