Manual regeneration of output at 1.48

src/ch02-00-guessing-game-tutorial.md

@@ -792,8 +792,8 @@ You guessed: 59
 You win!
 Please input your guess.
 quit
-thread 'main' panicked at 'Please type a number!: ParseIntError { kind: InvalidDigit }', src/libcore/result.rs:999:5
-note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
+thread 'main' panicked at 'Please type a number!: ParseIntError { kind: InvalidDigit }', src/main.rs:28:47
+note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 ```
 
 Typing `quit` actually quits the game, but so will any other non-number input.
@@ -866,6 +866,7 @@ foo
 ```console
 $ cargo run
    Compiling guessing_game v0.1.0 (file:///projects/guessing_game)
+    Finished dev [unoptimized + debuginfo] target(s) in 4.45s
      Running `target/debug/guessing_game`
 Guess the number!
 The secret number is: 61

src/ch05-01-defining-structs.md

@@ -204,8 +204,8 @@ itself. We’ll discuss traits in Chapter 10.
 >   |
 > help: consider introducing a named lifetime parameter
 >   |
-> 1 | struct User<'lifetime> {
-> 2 |     username: &'lifetime str,
+> 1 | struct User<'a> {
+> 2 |     username: &'a str,
 >   |
 >
 > error[E0106]: missing lifetime specifier
@@ -216,15 +216,15 @@ itself. We’ll discuss traits in Chapter 10.
 >   |
 > help: consider introducing a named lifetime parameter
 >   |
-> 1 | struct User<'lifetime> {
+> 1 | struct User<'a> {
 > 2 |     username: &str,
-> 3 |     email: &'lifetime str,
+> 3 |     email: &'a str,
 >   |
 >
 > error: aborting due to 2 previous errors
 >
 > For more information about this error, try `rustc --explain E0106`.
-> error: could not compile `structs`.
+> error: could not compile `structs`
 >
 > To learn more, run the command again with --verbose.
 > ```

src/ch09-01-unrecoverable-errors-with-panic.md

@@ -116,60 +116,25 @@ check the backtrace number mentioned in the text below the listing
 
 ```console
 $ RUST_BACKTRACE=1 cargo run
-thread 'main' panicked at 'index out of bounds: the len is 3 but the index is 99', /rustc/5e1a799842ba6ed4a57e91f7ab9435947482f7d8/src/libcore/slice/mod.rs:2806:10
+thread 'main' panicked at 'index out of bounds: the len is 3 but the index is 99', src/main.rs:4:5
 stack backtrace:
-   0: backtrace::backtrace::libunwind::trace
-             at /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
-   1: backtrace::backtrace::trace_unsynchronized
-             at /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
-   2: std::sys_common::backtrace::_print_fmt
-             at src/libstd/sys_common/backtrace.rs:84
-   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
-             at src/libstd/sys_common/backtrace.rs:61
-   4: core::fmt::ArgumentV1::show_usize
-   5: std::io::Write::write_fmt
-             at src/libstd/io/mod.rs:1426
-   6: std::sys_common::backtrace::_print
-             at src/libstd/sys_common/backtrace.rs:65
-   7: std::sys_common::backtrace::print
-             at src/libstd/sys_common/backtrace.rs:50
-   8: std::panicking::default_hook::{{closure}}
-             at src/libstd/panicking.rs:193
-   9: std::panicking::default_hook
-             at src/libstd/panicking.rs:210
-  10: std::panicking::rust_panic_with_hook
-             at src/libstd/panicking.rs:471
-  11: rust_begin_unwind
-             at src/libstd/panicking.rs:375
-  12: core::panicking::panic_fmt
-             at src/libcore/panicking.rs:84
-  13: core::panicking::panic_bounds_check
-             at src/libcore/panicking.rs:62
-  14: <usize as core::slice::SliceIndex<[T]>>::index
-             at /rustc/5e1a799842ba6ed4a57e91f7ab9435947482f7d8/src/libcore/slice/mod.rs:2806
-  15: core::slice::<impl core::ops::index::Index<I> for [T]>::index
-             at /rustc/5e1a799842ba6ed4a57e91f7ab9435947482f7d8/src/libcore/slice/mod.rs:2657
-  16: <alloc::vec::Vec<T> as core::ops::index::Index<I>>::index
-             at /rustc/5e1a799842ba6ed4a57e91f7ab9435947482f7d8/src/liballoc/vec.rs:1871
-  17: panic::main
-             at src/main.rs:4
-  18: std::rt::lang_start::{{closure}}
-             at /rustc/5e1a799842ba6ed4a57e91f7ab9435947482f7d8/src/libstd/rt.rs:67
-  19: std::rt::lang_start_internal::{{closure}}
-             at src/libstd/rt.rs:52
-  20: std::panicking::try::do_call
-             at src/libstd/panicking.rs:292
-  21: __rust_maybe_catch_panic
-             at src/libpanic_unwind/lib.rs:78
-  22: std::panicking::try
-             at src/libstd/panicking.rs:270
-  23: std::panic::catch_unwind
-             at src/libstd/panic.rs:394
-  24: std::rt::lang_start_internal
-             at src/libstd/rt.rs:51
-  25: std::rt::lang_start
-             at /rustc/5e1a799842ba6ed4a57e91f7ab9435947482f7d8/src/libstd/rt.rs:67
-  26: panic::main
+   0: rust_begin_unwind
+             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:483
+   1: core::panicking::panic_fmt
+             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/panicking.rs:85
+   2: core::panicking::panic_bounds_check
+             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/panicking.rs:62
+   3: <usize as core::slice::index::SliceIndex<[T]>>::index
+             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/slice/index.rs:255
+   4: core::slice::index::<impl core::ops::index::Index<I> for [T]>::index
+             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/slice/index.rs:15
+   5: <alloc::vec::Vec<T> as core::ops::index::Index<I>>::index
+             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/alloc/src/vec.rs:1982
+   6: panic::main
+             at ./src/main.rs:4
+   7: core::ops::function::FnOnce::call_once
+             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:227
+note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
 ```
 
 <span class="caption">Listing 9-2: The backtrace generated by a call to
@@ -181,7 +146,7 @@ information, debug symbols must be enabled. Debug symbols are enabled by
 default when using `cargo build` or `cargo run` without the `--release` flag,
 as we have here.
 
-In the output in Listing 9-2, line 17 of the backtrace points to the line in
+In the output in Listing 9-2, line 6 of the backtrace points to the line in
 our project that’s causing the problem: line 4 of *src/main.rs*. If we don’t
 want our program to panic, the location pointed to by the first line mentioning
 a file we wrote is where we should start investigating. In Listing 9-1, where

src/ch14-03-cargo-workspaces.md

@@ -151,7 +151,7 @@ function to call the `add_one` function, as in Listing 14-7.
 {{#rustdoc_include ../listings/ch14-more-about-cargo/listing-14-07/add/adder/src/main.rs}}
 ```
 
-<span class="caption">Listing 14-7: Using the `add-one` library crate from the 
+<span class="caption">Listing 14-7: Using the `add-one` library crate from the
  `adder` crate</span>
 
 Let’s build the workspace by running `cargo build` in the top-level *add*
@@ -216,7 +216,8 @@ crate:
 
 We can now add `use rand;` to the *add-one/src/lib.rs* file, and building the
 whole workspace by running `cargo build` in the *add* directory will bring in
-and compile the `rand` crate:
+and compile the `rand` crate. We will get one warning because we aren’t
+referring to the `rand` we brought into scope:
 
 <!-- manual-regeneration
 cd listings/ch14-more-about-cargo/no-listing-03-workspace-with-external-dependency/add
@@ -231,6 +232,16 @@ $ cargo build
    --snip--
    Compiling rand v0.5.6
    Compiling add-one v0.1.0 (file:///projects/add/add-one)
+warning: unused import: `rand`
+ --> add-one/src/lib.rs:1:5
+  |
+1 | use rand;
+  |     ^^^^
+  |
+  = note: `#[warn(unused_imports)]` on by default
+
+warning: 1 warning emitted
+
    Compiling adder v0.1.0 (file:///projects/add/adder)
     Finished dev [unoptimized + debuginfo] target(s) in 10.18s
 ```
@@ -255,7 +266,7 @@ error[E0432]: unresolved import `rand`
  --> adder/src/main.rs:2:5
   |
 2 | use rand;
-  |     ^^^^ no `rand` external crate
+  |     ^^^^ no external crate `rand`
 ```
 
 To fix this, edit the *Cargo.toml* file for the `adder` package and indicate

src/ch14-04-installing-binaries.md

@@ -33,7 +33,7 @@ $ cargo install ripgrep
   Installing ripgrep v11.0.2
 --snip--
    Compiling ripgrep v11.0.2
-    Finished release [optimized] target(s) in 3m 10s
+    Finished release [optimized + debuginfo] target(s) in 3m 10s
   Installing ~/.cargo/bin/rg
    Installed package `ripgrep v11.0.2` (executable `rg`)
 ```

src/ch15-01-box.md

@@ -192,7 +192,10 @@ after doing automatic regeneration, look at listings/ch15-smart-pointers/listing
 -->
 
 ```text
-  = help: insert indirection (e.g., a `Box`, `Rc`, or `&`) at some point to make `List` representable
+help: insert some indirection (e.g., a `Box`, `Rc`, or `&`) to make `List` representable
+  |
+2 |     Cons(i32, Box<List>),
+  |               ^^^^    ^
 ```
 
 In this suggestion, “indirection” means that instead of storing a value

src/ch20-02-multithreaded.md

@@ -616,6 +616,8 @@ warning: field is never read: `thread`
 49 |     thread: thread::JoinHandle<()>,
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
+warning: 3 warnings emitted
+
     Finished dev [unoptimized + debuginfo] target(s) in 1.40s
      Running `target/debug/main`
 Worker 0 got a job; executing.