This post deals with standard library collections, and corresponds to chapter 16. in the Programming Rust book.
Rust moves elements into collections to avoid deep-copying of values. Due to Rusts borrow checker we won't get dangling pointers while collections are changed or resized.
We've used that one …
I'm working through chapter 15, "Iterators" in the Programming Rust book for this post.
Iterators produce sequences of values, and all kinds of things can be iterated over – strings, collection types, files, connections, database records, etc.
Rust iterators have a rich set of methods like fold(), map(),
filter(), reduce …
For this post I'm looking at Chapter 14. Closures in the Rust Programming Book. A whole chapter dedicated to closures, count me in!
Rust closures can capture vars from the enclosing scope, as in other languages.
By default closures borrow refs to captured vars …
For this post I'm looking at Chapter 13. Utility Traits in the Programming Rust book.
I don't expect radically new stuff here – but, given the importance of traits, rather some practical things into how idiomatic Rust should look like.
The book defines three broad categories of utility traits:
This installement of my Rust learning series deals with Chapter 12. Operator Overloading
I'm actually a bit wary of operator overloading, as it's easily ab/overused, and objects then behaving in a opaque "magical" way. Sometimes it's just clearer to spell a method out instead of binding it to …
This post corresponds to Chapter 11. Traits and Generics.
Traits are like interfaces or abstract base classes – contracts that describe what a type can do by describing it's methods. Optionally, they can also define default implementations of the methods they prescribe.
An example trait:
trait Write {
fn write(&mut …This post corresponds to Chapter 10. Enums and Patterns.
Rusts enums are like C unions: they can be one of several kinds of data.
Patterns in Rust resemble the ones in Erlang; they allow to match on parts of a data structure and bind parts of it to variables …
This post corresponds to Chapter 9. Structs in the "Programming Rust" book.
Rust structs are data collection; fields can be named or tuple (or there can be no fields at all). Like in Go, you can have methods bound to structs (there is no separate "class" concept).
This post corresponds to "Chapter 8. Crates and Modules" in the book.
Crates are the package format for Rust; they're made up of
source code plus tests, data, etc. Managing those
packages is the job of cargo, came across this previously. Building
crates is triggered by running cargo …
This post corresponds to "Chapter
7. Error Handling" in the book. It's a short chapter on Rusts panic and Result types.
Unlike Python, and similar to Go, Rust doesn't use Exceptions to handle errors. Instead, "expected" errors (things like EPERM or ENOENT, i.e. stuff that just can happen …