I'm reading the section on ownership. Valgrind usually thinks my 'modern C++' code is leak free, and when it complains I understand why, so I'm not a complete stranger to systems programming. But for whatever reason I have always run into a brick wall with rusts strange compiler messages regarding lifetimes. I read the previous books bit on ownership. I'm not sure if this new version is better written or I've come ac…
Next Iteration of “The Rust Programming Language” Book
21–30 of 111 posts
Re: Next Iteration of “The Rust Programming Language” Book
#22Another excellent book is "Programming Rust"[1], especially if you already know C/C++ 1 - http://shop.oreilly.com/product/0636920040385.do
Re: Next Iteration of “The Rust Programming Language” Book
#23This book has been hugely helpful for me to get started in Rust. I've been following since the original "Rust for Rubyists" from Steve Klabnik. Steve if you are listening, thanks for putting all the hard work into the original book, the revision as The Rust Programming Language, and this most recent revision.
Thanks to Steve and also carols10cents for this excellent revision.
Re: Next Iteration of “The Rust Programming Language” Book
#24This new book isn't finished yet, is it? If I remember correctly [0], there were several more chapters to go, and a likely timeline of months... [0] https://github.com/rust-lang/book/issues
I am forbidden by my coauthor to prognosticate about due dates, but let's just say that... well, I won't say anything ;)
I'm almost done with the first draft of chapter 15.
Re: Next Iteration of “The Rust Programming Language” Book
#25Another excellent book is "Programming Rust"[1], especially if you already know C/C++ 1 - http://shop.oreilly.com/product/0636920040385.do
I wish there were 50 books on Rust. :)
Re: Next Iteration of “The Rust Programming Language” Book
#26Another excellent book is "Programming Rust"[1], especially if you already know C/C++ 1 - http://shop.oreilly.com/product/0636920040385.do
So, if I want the paper book when it's out, and to read the early release ebook now, do I have to pay twice?
Re: Next Iteration of “The Rust Programming Language” Book
#27This new book isn't finished yet, is it? If I remember correctly [0], there were several more chapters to go, and a likely timeline of months... [0] https://github.com/rust-lang/book/issues
> a likely timeline of months... I am forbidden by my coauthor to prognosticate about due dates, but let's just say that... well, I won't say anything ;) I'm almost done with the first draft of chapter 15.
TRUE FACT. Everyone here knows how hard it is to estimate, we'll let everyone know once it's done instead :)
Re: Next Iteration of “The Rust Programming Language” Book
#28Re: Next Iteration of “The Rust Programming Language” Book
#29I'm reading the section on ownership. Valgrind usually thinks my 'modern C++' code is leak free, and when it complains I understand why, so I'm not a complete stranger to systems programming. But for whatever reason I have always run into a brick wall with rusts strange compiler messages regarding lifetimes. I read the previous books bit on ownership. I'm not sure if this new version is better written or I've come ac…
Lifetimes can be confusing as hell, especially declaring them correctly. It looks like section 10.3 in this new book improves things.
We decided to do it this way so that you can write real Rust code without going "what is that syntax"; you don't need to have a full understanding of the more exotic aspects of lifetimes to write useful code in Rust.
Re: Next Iteration of “The Rust Programming Language” Book
#30I'm reading the section on ownership. Valgrind usually thinks my 'modern C++' code is leak free, and when it complains I understand why, so I'm not a complete stranger to systems programming. But for whatever reason I have always run into a brick wall with rusts strange compiler messages regarding lifetimes. I read the previous books bit on ownership. I'm not sure if this new version is better written or I've come ac…
Lifetimes can be confusing as hell, especially declaring them correctly. It looks like section 10.3 in this new book improves things.