Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Next Iteration of “The Rust Programming Language” Book

rust-lang.github.io

Post reply on HN
Print view View original

61–70 of 111 posts

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

#61

Post by flukus »

purple-again wrote: post #3

Sigh. Looks like it's time for round 5 of time to learn Rust(my personal failing, not meant as a slight against the language at all). Has the pace of sweeping changes to the language slowed down in the past year? I rode the Ember train from 1.4 to now and it was an extremely ehausting process to get to 2.0 with nearly every version requiring frustrating architectural rewrites. The upgrade from 2.0 to 2.8 took like 15…

In my very limited experience, the libraries still aren't stable. I ran into a bunch of errors a couple of days ago because my distro was on 1.14 rust compiler but the latest was 1.15. I'm not sure exactly what the issue is but it looked like the standard libraries had changed between versions.

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

#62

Post by flukus »

lacampbell wrote: post #7

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…

I've just been through this section. I'd love a separate tutorial just for the borrowing lifetimes and error handling that make rust different.

It's to easy to go though the current tutorial and think "wow, this is easy and makes sense" only to come completely undone when you try to do something.

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

#63

Post by steveklabnik »

flukus wrote: post #61
purple-again wrote: post #3

Sigh. Looks like it's time for round 5 of time to learn Rust(my personal failing, not meant as a slight against the language at all). Has the pace of sweeping changes to the language slowed down in the past year? I rode the Ember train from 1.4 to now and it was an extremely ehausting process to get to 2.0 with nearly every version requiring frustrating architectural rewrites. The upgrade from 2.0 to 2.8 took like 15…

In my very limited experience, the libraries still aren't stable. I ran into a bunch of errors a couple of days ago because my distro was on 1.14 rust compiler but the latest was 1.15. I'm not sure exactly what the issue is but it looked like the standard libraries had changed between versions.

1.15 contained a new feature that was seriously awaited, so a lot of libraries pushed out a new version using that feature. Even with that, though, Cargo _should_ have saved you here, via the lockfile.

It shouldn't have been the standard library though. If it was, that'd be a serious bug! If you do figure it out, and it is the standard library, please file a bug. And if you need any help, feel free to reach out. I'm here to help.

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

#64

Post by pcwalton »

flukus wrote: post #61
purple-again wrote: post #3

Sigh. Looks like it's time for round 5 of time to learn Rust(my personal failing, not meant as a slight against the language at all). Has the pace of sweeping changes to the language slowed down in the past year? I rode the Ember train from 1.4 to now and it was an extremely ehausting process to get to 2.0 with nearly every version requiring frustrating architectural rewrites. The upgrade from 2.0 to 2.8 took like 15…

In my very limited experience, the libraries still aren't stable. I ran into a bunch of errors a couple of days ago because my distro was on 1.14 rust compiler but the latest was 1.15. I'm not sure exactly what the issue is but it looked like the standard libraries had changed between versions.

That's forwards compatibility, not backwards compatibility.

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

#65

Post by TheCoreh »

steveklabnik wrote: post #28

Both carols10cents and I, the primary authors, are reading this thread. Happy to answer any questions other than "when will it be done," as estimations are hard ;)

Are you interested in translating the book to other languages? Is such a project already underway? I can help with Portuguese

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

#66

Post by carols10cents »

TheCoreh wrote: post #65
steveklabnik wrote: post #28

Both carols10cents and I, the primary authors, are reading this thread. Happy to answer any questions other than "when will it be done," as estimations are hard ;)

Are you interested in translating the book to other languages? Is such a project already underway? I can help with Portuguese

Yes we are! There's someone working on Vietnamese [1]. It's a bit blocked on mdbook support [2], but the translation part could start before that's done. Chapters 2, 3, 4, and 6 are effectively "frozen" for print at this point [3] so they'd be the place I'd recommend starting first!

[1] - https://github.com/rust-lang/book/issues/375

[2] - https://github.com/azerupi/mdBook/pull/200

[3] - https://github.com/rust-lang/book/projects/1

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

#67

Post by [deleted] »

TheCoreh wrote: post #65
steveklabnik wrote: post #28

Both carols10cents and I, the primary authors, are reading this thread. Happy to answer any questions other than "when will it be done," as estimations are hard ;)

Are you interested in translating the book to other languages? Is such a project already underway? I can help with Portuguese

[deleted]

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

#68

Post by flukus »

steveklabnik wrote: post #63
flukus wrote: post #61

Earlier quoted context omitted.

In my very limited experience, the libraries still aren't stable. I ran into a bunch of errors a couple of days ago because my distro was on 1.14 rust compiler but the latest was 1.15. I'm not sure exactly what the issue is but it looked like the standard libraries had changed between versions.

1.15 contained a new feature that was seriously awaited, so a lot of libraries pushed out a new version using that feature. Even with that, though, Cargo _should_ have saved you here, via the lockfile. It shouldn't have been the standard library though. If it was, that'd be a serious bug! If you do figure it out, and it is the standard library, please file a bug. And if you need any help, feel free to reach out. I'm…

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.

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

#69

Post by dbaupp »

steveklabnik wrote: post #59
jayflux wrote: post #55

Earlier quoted context omitted.

Thanks! I would absolutely love a single webpage version, that would be even better

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"

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

#70

Post by steveklabnik »

flukus wrote: post #68
steveklabnik wrote: post #63

Earlier quoted context omitted.

1.15 contained a new feature that was seriously awaited, so a lot of libraries pushed out a new version using that feature. Even with that, though, Cargo _should_ have saved you here, via the lockfile. It shouldn't have been the standard library though. If it was, that'd be a serious bug! If you do figure it out, and it is the standard library, please file a bug. And if you need any help, feel free to reach out. I'm…

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?

Post reply on HN