4 ms·
Hi all! As always, happy to answer questions here.
by steveklabnik 10y ago
Hi all! As always, happy to answer questions here.
- kevinmgranger 10y agoThe Rust Programming Language remains as one of the best introductions I've had to a new programming language. I thank you for your work on it.
- steveklabnik 10y agoThank you so much. :)
- bluejekyll 10y agoYes, and the work on the documentation in general. It's amazing. So many other young languages are crap in this area, even mature ones. I think the thing that makes Rust amazing is that it's young, and yet well documented, making it easier to get started. Can't thank you enough, nice work.
- sdegutis 10y agoSlightly off topic, but the previous blog post's embedded tweet isn't centered like it seems like it was meant to be. Just caught me off guard and figured I should mention it.
- steveklabnik 10y agoThanks, I'll check it out. Dunno what's up. Gah!
- code18 10y agoJust a quick comment, there's no date on the post, at least when viewing it via mobile. It's kinda important when you're reading an article with the title "what's new ... ". :)
- AndrewGaspar 10y agoIt does this weird thing on desktop where the date is barely visible above the title until you mouse over it. Not sure why.
- kbenson 10y agoI don't understand why so many blog platforms choose to hide or obscure the timestamp of the post. It's like they don't consider whether something is current as relevant, like every since post they contain is some timeless pearl of wisdom meant to withstand the test of time and be just as useful a few years down the road. Or maybe it's just a nod in the direction of truth, as the author can often change the post after it is initially published, or even just change the date to be whatever they want.
- steveklabnik 10y agoThanks! This is Svbtle, so I can't control that, but it's right above the title; though it's a light-gray until you hover. August 15, 2016, for posterity's sake. :)
- code18 10y agoOkay just noticed it :) Thanks!
- davegauer 10y agoAt a glance, the new material looks excellent, especially liking the illustrations in the Ownership chapter! This couldn't have come at a better time for me. I started learning Rust in August 2015 from TRPL, but life got in the way. Now I've started up again, so I'm very excited about the documentation updates.
- steveklabnik 10y agoThank you, I spent a bunch of time fighting graphviz to make them.
- wasd 10y agoRead through the Rust book and really enjoyed it. Curious when you think the next rewrite will be done.
- steveklabnik 10y agoI am trying to shoot for roughly the end of the year.
- Eridrus 10y agoIt's been about a year since I wrote any Rust, but one of the things I struggled with is having an intuition for the "right way" of dealing with the borrow checker. I often found myself storing indexes into vectors/maps and not being sure if this was a good way of doing things; it seemed better than raw pointers in some senses, but it also felt like I was just bypassing the borrow checker and using a system that had less drastic failure modes, but othewise no guarantees. I also found myself building up datastructures of these indexes that I would not have had to do in a traditional imperative language. I would have really appreciated some examples of writing your own data structures where a traditional encoding would run into the borrow checker (eg graphs).
- steveklabnik 10y agoThanks, totally hear that. We should promote http://cglab.ca/~abeinges/blah/too-many-lists/book/ http://cglab.ca/~abeinges/blah/too-many-lists/book/ more...
- Eridrus 10y agoI had a brief glance at this and while this seems to present a continuous story, I had to read all the way to section 2.4 to learn anything new (mem::replace) without any idea of whether I would. I would have prefered a reference book of techniques with examples to this format, though maybe starting with a ToC of techniques would be better than a rant about linked lists. [EDIT]: I read some more and this seems like really useful info... just not advertised or IMO presented well.
- caconym_ 10y agoYes! This document was instrumental for me in getting my foot in the door of understanding how to use memory in Rust.
- carols10cents 10y agoI agree with Steve that you'll probably love the "Learning Rust With Entirely Too Many Linked Lists" that he linked to. While not as complex as that, I would like to hear what you think about the slices section in the new version of the book: http://rust-lang.github.io/book/ch04-03-slices.html http://rust-lang.github.io/book/ch04-03-slices.html It introduces slices by starting with functions that use indexes into `String`s, which sounds similar to what you were doing. It demonstrates the problems with that approach, and then shows how to use slices instead. I'm not sure if slices would have worked well in your cases, but this chapter is so similar to what you said I wanted to point it out!