Hands-on Rust: Various Typos/Notes B3.0

I am working my way through the book. Things are going well and content looks good overall. I have spotted a few typos/concerns you may be interested in. Thanks for the hard work!

re: hands-on-rust_B3.0.pdf

p59 typo
“Alternatively, you can Alternatively, you can”

p96 typo
“…it’s time to make the build constructor for you MapBuilder class.”

p106
“Systems query the entities and components”
Is the queries arrow between Componenets and Systems backwards? Or it could be labelled “Query results”?

p109 typo
“You’re no longer be treating the player as a special case”

p112 typo
“Calling push() create a new Entity…”
and
“associated with the new it.”

p109 discrepancy with p113

  • p109resources is still in state on p109 and looks required for insertion of map and camera
  • p113 resources is not present in strunct State code snippet

p117 awk
“Multiple systems can access a read-only
component at once, but only a single system can write to a component type
at once (and prevents read-only access from running until it is finished—pre-
venting a system from encountering data that changed part of the way through
system execution).”

p119 typo
“If you need to filter on the component’s content, you
canuse the iterator’s…”

p121
code snippet and paragraph above does not include: use crate::prelude::*;
code snippet does not compile without it.
p122 does include the prelude in the code

p126
I cannot find graphic shown on page. I used one from
/code/EntitiesComponentsAndSystems/dungeonecs/resources/
but it is not identical to what is on p126

p138 typo
“You know sure that a turn state exists, so you can skip error
checking for once.”

p143 typo
“… is simplified to no longer need write-access to Point and not need the map at all:”

1 Like

Thank you! I’ve added this into the issue tracker, and I’ll try and get them fixed up for beta 4 (working on that today; the cut-off is coming up, so I apologize if any of them end up in beta 5 instead).