b'

Something borrowed, something\\u2026 moved?

Subject: The struct data type constructor, and the basics of Rust\\u2019s \\u201cownership\\u201d concept and \\u201cborrowing\\u201d and \\u201cmoving\\u201d.

Follow/Support

\\n
• New Rustacean:\\n
  \\n
  • Twitter: @newrustacean
  \\n
  • App.net: @newrustacean
  \\n
  • Patreon
  \\n
  • Email: hello@newrustacean.com
  \\n
\\n
• Chris Krycho\\n
  \\n
  • Twitter: @chriskrycho
  \\n
  • App.net: @chriskrycho
  \\n
\\n

Notes

Today\\u2019s episode discusses, and the associated source code demonstrates, a few basic behaviors of structs\\u2026 including borrowing!

After taking a short look at one of Rust\\u2019s 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\\u2019m not getting into things like heap-allocated memory (Box) or dealing with move semantics with threads or closures. (I haven\\u2019t actually figured those out well enough yet to write something like this for them!)

As usual, you\\u2019ll want to have the src open to see what I\\u2019m doing with the components documented below.

Links

\\n
• rustfmt \\u2013 a tool for formatting Rust code\\n
  \\n
  • repo
  \\n
  • \\u201crustfmt-ing Rust`
  \\n
  • Reddit discussion
  \\n
\\n
• RFC for incremental compilation\\n
  \\n
  • Text of the RFC
  \\n
  • GitHub pull request
  \\n
\\n