Render mdBook for b84811e

microsoft · Feb 9, 2024 · 8960f30 · 8960f30
1 parent 092be72
commit 8960f30
Show file tree

Hide file tree

Showing 5 changed files with 8 additions and 8 deletions.
diff --git a/latest/linq/index.html b/latest/linq/index.html
@@ -474,7 +474,7 @@ <h2 id="iterator-methods-yield"><a class="header" href="#iterator-methods-yield"
 <code>IEnumerable&lt;T&gt;</code> or an <code>IEnumerator&lt;T&gt;</code>. The compiler then converts the body
 of the method into a concrete implementation of the return type, instead of
 the developer having to write a full-blown class each time.
-<em><a href="https://doc.rust-lang.org/stable/unstable-book/language-features/generators.html">Generators</a></em>, as they're called in Rust, are still considered
+<em><a href="https://doc.rust-lang.org/unstable-book/language-features/coroutines.html">Coroutines</a></em>, as they're called in Rust, are still considered
 an unstable feature at the time of this writing.</p>
 
                     </main>

diff --git a/latest/print.html b/latest/print.html
@@ -2188,7 +2188,7 @@ <h2 id="custom-conversion"><a class="header" href="#custom-conversion">Custom co
 fn main() {
     let (tx, rx) = mpsc::channel();
 
-    let procuder = thread::spawn(move || {
+    let producer = thread::spawn(move || {
         for n in 1..10 {
             tx.send(format!(&quot;Message #{}&quot;, n)).unwrap();
         }
@@ -2199,7 +2199,7 @@ <h2 id="custom-conversion"><a class="header" href="#custom-conversion">Custom co
         println!(&quot;{}&quot;, received);
     }
 
-    procuder.join().unwrap();
+    producer.join().unwrap();
 }</code></pre>
 <p>Like channels in Rust, .NET also offers channels in the
 <code>System.Threading.Channels</code> namespace, but it is primarily designed to be used
@@ -2936,7 +2936,7 @@ <h2 id="iterator-methods-yield"><a class="header" href="#iterator-methods-yield"
 <code>IEnumerable&lt;T&gt;</code> or an <code>IEnumerator&lt;T&gt;</code>. The compiler then converts the body
 of the method into a concrete implementation of the return type, instead of
 the developer having to write a full-blown class each time.
-<em><a href="https://doc.rust-lang.org/stable/unstable-book/language-features/generators.html">Generators</a></em>, as they're called in Rust, are still considered
+<em><a href="https://doc.rust-lang.org/unstable-book/language-features/coroutines.html">Coroutines</a></em>, as they're called in Rust, are still considered
 an unstable feature at the time of this writing.</p>
 <div style="break-before: page; page-break-before: always;"></div><h1 id="meta-programming"><a class="header" href="#meta-programming">Meta Programming</a></h1>
 <p>Metaprogramming can be seen as a way of writing code that writes/generates other

diff --git a/latest/searchindex.js b/latest/searchindex.js
diff --git a/latest/searchindex.json b/latest/searchindex.json
diff --git a/latest/threading/producer-consumer.html b/latest/threading/producer-consumer.html
@@ -184,7 +184,7 @@ <h1 id="producer-consumer"><a class="header" href="#producer-consumer">Producer-
 fn main() {
     let (tx, rx) = mpsc::channel();
 
-    let procuder = thread::spawn(move || {
+    let producer = thread::spawn(move || {
         for n in 1..10 {
             tx.send(format!(&quot;Message #{}&quot;, n)).unwrap();
         }
@@ -195,7 +195,7 @@ <h1 id="producer-consumer"><a class="header" href="#producer-consumer">Producer-
         println!(&quot;{}&quot;, received);
     }
 
-    procuder.join().unwrap();
+    producer.join().unwrap();
 }</code></pre>
 <p>Like channels in Rust, .NET also offers channels in the
 <code>System.Threading.Channels</code> namespace, but it is primarily designed to be used