> I suppose I could skip to whatever chapter seems appealing rather  than reading page by page...

I do this on these types of books, which causes me to miss stuff and be an ignorant coder, because I am also too lazy to scroll back.

So honestly, if you have the discipline to keep a list of open items and work through it sequentially, that's probably better in the end. Saves trial & error later.

"The Rust Programming Language" is what I was reading page by page, but my mind wanted answers to certain questions. 

I suppose I could skip to whatever chapter seems appealing rather  than reading page by page...

nerd2ninja

I need you guys to tell me how much I suck

... but you're awesome too because you're asking good questions that many devs don't even think of asking.

It goes into some deeper detail on how variable assignments work, eg 

devs

Learning Embedded Rust

> I need you guys to tell me how much I suck

You Suck!

... but you're awesome too because you're asking good questions that many devs don't even think of asking.

Did you try ["The Rust Programming Language"](https://doc.rust-lang.org/stable/book/title-page.html)?

It goes into some deeper detail on how variable assignments work, eg [Variables and Mutability](https://doc.rust-lang.org/stable/book/ch03-01-variables-and-mutability.html#variables-and-mutability)