From fa7ba34dd2d3e5247cd18c6e34656c07cf1a3eb0 Mon Sep 17 00:00:00 2001 From: David Wickes Date: Sun, 12 Mar 2017 14:20:17 +0000 Subject: [PATCH] fixes missing reference to ch 13 --- .../src/ch12-03-improving-error-handling-and-modularity.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/second-edition/src/ch12-03-improving-error-handling-and-modularity.md b/second-edition/src/ch12-03-improving-error-handling-and-modularity.md index ffcdb7779..716d7ecf0 100644 --- a/second-edition/src/ch12-03-improving-error-handling-and-modularity.md +++ b/second-edition/src/ch12-03-improving-error-handling-and-modularity.md @@ -163,9 +163,9 @@ code very straightforward. > #### The Tradeoffs of Using `clone` > > There's a tendency amongst many Rustaceans to prefer not to use `clone` to fix -> ownership problems due to its runtime cost. In Chapter XX on iterators, we'll -> learn how to make this situation more efficient. For now, it's okay to copy a -> few strings to keep making progress. We're only going to be making these +> ownership problems due to its runtime cost. In Chapter 13 we'll learn how to +> make this situation more efficient with iterators. For now, it's okay to copy +> a few strings to keep making progress. We're only going to be making these > copies once, and our filename and search string are both very small. It's > better to have a working program that's a bit inefficient than try to > hyper-optimize code on your first pass. As you get more experienced with Rust,