:)

Makes sense, thanks a lot. Pretty much what I’ve gathered during the month as well. Error handling is a pretty big part of the philosophy of any language, and usually it takes time to untangle. :)

Yeah, the difficulty in the beginning in a new language is to tell what’s what first :) New terminology, different way of thinking. Rust brings a lot of concepts to the table that I needed time to internalize.

Thanks a lot for the notes, these are the things that I kinda picked up as well along the way!

Yeah, I find the docs a bit lacking and sometimes misleading. Quite often when I wanted to do anything even slightly different from the example given I ended up running into an issue that calls for a whole different approach of implementing the original example. I guess the language is moving really fast, and time is spent more on development than documentation. It’s mostly up to the users at this point to do the documentation

Also wrote up the results of this month’s learning at https://gergely.imreh.net/blog/2015/12/lotm-rust-results/

Wrote up the results of this month’s learning at https://gergely.imreh.net/blog/2015/12/lotm-rust-results/ Hope there will be something interesting… Mostly went through the tutorial in detail (lots of side track and experimentation), plus doing a small project.

Thanks a lot! Since writing this post I understood a lot more, and it makes all the sense. I guess it’s mostly the new terminology that took me a while to turn into mental models.

Wrote up the results of this month’s learning at https://gergely.imreh.net/blog/2015/12/lotm-rust-results/

You would probably not use unwrap() in production code because of the possibility for it to return an Err and crash. In production code you’d want to have a match case to handle the Err result, or use something like unwrap_or() to return another value if the Result is type Err.