Chris Krycho

@iamnbutler sorry for the delay in response—busy couple of weeks! * **Who has the most intuitive test runner?** I don’t know that any of them are actually *great*, but/and they’ve...

@Polve good questions, but better served by opening a Discussion, so please move there! Thanks!

Relevant: #3331.

You are correct! I think at this point in the book most people realize they need to add dependencies for things to work, but we might still want to be...

Thanks for opening the issue. I agree that the wording could be improved here, but as you discovered, it will be tricky to get it just right! Flagging it up...

Thanks! I agree that this is a bit confusing, and at first blush your suggestion is a nice improvement. We'll chat and see if we want to run with that...

Thanks for this and #3820. I think we probably don’t want to add more *example code* here, but maybe we can sneak in a sentence which says that `continue` and...

As, I think, one of the people who has done the _most_ thinking about “how to say Rust code in a way that doesn’t assume you are looking at it/can...

For reference for myself and @carols10cents, see my comment over on #3821: I think we can write a single sentence that addresses this, probably.

@cyrilberrypi not sure what you're asking! You might want to read [Looping Through a Collection with `for`](https://doc.rust-lang.org/book/ch03-05-control-flow.html?highlight=range#looping-through-a-collection-with-for) in this book, or [a similar example in Rust by Example](https://doc.rust-lang.org/stable/rust-by-example/flow_control/for.html). If you...