Live data from Hacker News

Next Iteration of “The Rust Programming Language” Book

rust-lang.github.io

71–80 of 111 posts

Re: Next Iteration of “The Rust Programming Language” Book

#71
post #69

Earlier quoted context omitted.

You can click the "print" button in the upper right hand corner, which gives you http://rust-lang.github.io/book/print.html

For some reason that page has the title "Macros - The Rust Programming Language"

Weird, I'll file a bug, thanks.

Re: Next Iteration of “The Rust Programming Language” Book

#73
post #68

Earlier quoted context omitted.

This was using the latest toml and serde releases, which I think does use that new attribute stuff (which is fucking cool btw). But no warning from cargo until it was compiling the dependencies.

Yeah, that makes sense, they would totally be using it. Still, upgrading to those releases _should_ have taken manual intervention; how were you depending on them in your Cargo.toml? And I guess you had no Cargo.lock for some reason?

Brand new project. I added them by putting the dependencies into the cargo.toml file (with the current version), is that how you're meant to add them or is there some kind of "cargo install" command?

Re: Next Iteration of “The Rust Programming Language” Book

#75
post #34
post #32

I had tried running Rust for a few months now, but it didn't really clicked until I went through this book. Thanks to the great explanations of the concepts of rust, the helpful exercises and examples, I have not only since been able to contribute to the RustLang, but also am in the process of a PR for Servo, created a website using rocket.rs, and started using Rust at work. It's definitely true that the initial hump…

Which book did you read this one or the stable one: https://doc.rust-lang.org/doc/stable/book/ They aren't the same.

This unfinished one. Despite being unfinished, I still preferred the content over the current official one.

Re: Next Iteration of “The Rust Programming Language” Book

#76

Another excellent book is "Programming Rust"[1], especially if you already know C/C++ 1 - http://shop.oreilly.com/product/0636920040385.do

I've been reading the early access version for a while now, and it is excellent . I hadn't had much luck with the "official" documentation, previously. Jim Blandy's writing is an exemplar for good teaching technique, and this book is shaping up to be the go-to recommendation for learning Rust, in my opinion.

I have been reading it as well. For my taste, it is a bit too verbose.

I like to see something along the lines of the K&R book or the GoPL book. I was hoping that "Programming Rust" is such a book, but I was disappointed. And (may be it is just me) I like to see exercises in Programming books.

Re: Next Iteration of “The Rust Programming Language” Book

#77
post #73

Earlier quoted context omitted.

Yeah, that makes sense, they would totally be using it. Still, upgrading to those releases _should_ have taken manual intervention; how were you depending on them in your Cargo.toml? And I guess you had no Cargo.lock for some reason?

Brand new project. I added them by putting the dependencies into the cargo.toml file (with the current version), is that how you're meant to add them or is there some kind of "cargo install" command?

Ah ha! Yeah, so it makes sense that the latest version would need the latest version of the compiler. You could use the previous version and it should still work. Usually, when a project requires a new Rust version, there's a bump to whichever version determines compatibility. (for x.y.z, x if x != and y if x == 0) Given that you said it was breaking, I thought you meant you had a project that suddenly stopped working, my bad.

For now, that's the standard way, at some point, we might pull a "cargo add" command into core, but there's some blocking on parsing.

Re: Next Iteration of “The Rust Programming Language” Book

#79
Something I'm curious about is why this next iteration of the Rust Programming Language book has been developed relatively hidden away from new folks, who have to continue using the old book unless they stumble upon the new one somehow.

I would think that if the content of the new book does a better job at educating new users of the language, you would want that to be in front of everybody as absolutely soon as possible.

With that in mind, why is the strategy to complete the new book entirely before moving over? If the new one has such big gaps that it can't stand on its own, why not try some gradual migration?

Re: Next Iteration of “The Rust Programming Language” Book

#80

Something I'm curious about is why this next iteration of the Rust Programming Language book has been developed relatively hidden away from new folks, who have to continue using the old book unless they stumble upon the new one somehow. I would think that if the content of the new book does a better job at educating new users of the language, you would want that to be in front of everybody as absolutely soon as possi…

> why this next iteration of the Rust Programming Language book has been developed relatively hidden away from new folks, who have to continue using the old book unless they stumble upon the new one somehow

Because it is not done yet.

Post reply on HN