Multithreading: Update compiler error messages

They have a new format.

Author: dbrgn

sections/multithreaded.tex

@@ -27,23 +27,32 @@ \section{Multithreaded Programming}
 \end{minted}
 \sep
 \begin{minted}[fontsize=\footnotesize]{text}
-error: closure may outlive the current function, but it borrows `data`,
-which is owned by the current function [E0373]
-    let t1 = thread::spawn(|| {
-        data.push(19);
-    });
-note: `data` is borrowed here
-    data.push(19);
-    ^~~~
-help: to force the closure to take ownership of `data` (and any other
-referenced variables), use the `move` keyword, as shown:
-     let t1 = thread::spawn(move || {
-         data.push(19);
-     });
+error[E0373]: closure may outlive the current function, but it borrows `data`,
+              which is owned by the current function
+ --> src/main.rs:5:28
+  |
+5 |     let t1 = thread::spawn(|| { data.push(19); });
+  |                            ^^   ---- `data` is borrowed here
+  |                            |
+  |                            may outlive borrowed value `data`
+  |
+note: function requires argument type to outlive `'static`
+ --> src/main.rs:5:14
+  |
+5 |     let t1 = thread::spawn(|| { data.push(19); });
+  |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 \end{minted}
 \end{frame}
 
 \begin{frame}[fragile]{Shared Data (2) -- Move data}
+The compiler also gives us a helpful hint:
+\begin{minted}[fontsize=\footnotesize]{text}
+help: to force the closure to take ownership of `data` (and any
+      other referenced variables), use the `move` keyword
+  |
+5 |     let t1 = thread::spawn(move || { data.push(19); });
+  |                            ^^^^^^^
+\end{minted}
 Let's move the \texttt{data} into the Thread.
 \begin{minted}{rust}
 let mut data = vec![0];
@@ -61,14 +70,16 @@ \section{Multithreaded Programming}
 \end{minted}
 \sep
 \begin{minted}[fontsize=\footnotesize]{text}
-error: use of moved value: `data` [E0382]
-    println!("Data: {:?}", data);
-                           ^~~~
-note: `data` moved into closure environment here because it has
-type `collections::vec::Vec<i32>`, which is non-copyable
-    let t1 = thread::spawn(move || { data.push(19); });
-                           ^~~~~~~~~~~~~~~~~~~~~~~~~~
-help: perhaps you meant to use `clone()`?
+error[E0382]: borrow of moved value: `data`
+4 |     let mut data = vec![0];
+  |         -------- move occurs because `data` has type `std::vec::Vec<i32>`,
+  |                  which does not implement the `Copy` trait
+5 |     let t1 = thread::spawn(move || { data.push(19); });
+  |                            -------   ---- variable moved due to use
+  |                            |              in closure
+  |                            value moved into closure here
+7 |     println!("Data: {:?}", data);
+  |                            ^^^^ value borrowed here after move
 \end{minted}
 \end{frame}
 
@@ -96,19 +107,19 @@ \section{Multithreaded Programming}
 \begin{minted}{rust}
 let data = Arc::new(vec![0]);
 
-let mut data2 = data.clone();
-let t1 = thread::spawn(move || {
-    data2.push(1);
-});
+let data2 = data.clone();
+let t1 = thread::spawn(move || { data2.push(1); });
 
 t1.join().unwrap();
 println!("Data: {:?}", data);
 \end{minted}
 \sep
 \begin{minted}[fontsize=\footnotesize]{text}
-error: cannot borrow immutable borrowed content as mutable
-    data2.push(1);
-    ^~~~~
+error[E0596]: cannot borrow data in a `&` reference as mutable
+ --> src/main.rs:8:38
+  |
+8 |     let t1 = thread::spawn(move || { data2.push(1); });
+  |                                      ^^^^^ cannot borrow as mutable
 \end{minted}
 \end{frame}
 
@@ -123,7 +134,7 @@ \section{Multithreaded Programming}
 });
 
 t1.join().unwrap();
-println!("Data: {:?}", *data.lock().unwrap());
+println!("Data: {:?}", data.lock().unwrap());
 \end{minted}
 \sep
 \begin{minted}[fontsize=\footnotesize]{text}