Correct rust code block in *Dataflow Analysis*

src/SUMMARY.md

@@ -194,7 +194,7 @@
 
 - [Prologue](./part-5-intro.md)
 - [MIR optimizations](./mir/optimizations.md)
-- [Debugging](./mir/debugging.md)
+- [Debugging MIR](./mir/debugging.md)
 - [Constant evaluation](./const-eval.md)
     - [Interpreter](./const-eval/interpret.md)
 - [Monomorphization](./backend/monomorph.md)

src/mir/dataflow.md

@@ -127,16 +127,18 @@ value will be `true`, since our analysis is done as soon as we determine that
 `transmute` has been called. Our join operator will just be the boolean OR (`||`)
 operator. We use OR and not AND because of this case:
 
-```
+```rust
+# unsafe fn example(some_cond: bool) {
 let x = if some_cond {
-    std::mem::transmute<i32, u32>(0_i32); // transmute was called!
+    std::mem::transmute::<i32, u32>(0_i32) // transmute was called!
 } else {
-    1_u32; // transmute was not called
+    1_u32 // transmute was not called
 };
 
 // Has transmute been called by this point? We conservatively approximate that
 // as yes, and that is why we use the OR operator.
 println!("x: {}", x);
+# }
 ```
 
 ## Inspecting the Results of a Dataflow Analysis
@@ -219,7 +221,7 @@ the example below:
 
 ["gen-kill" problems]: https://en.wikipedia.org/wiki/Data-flow_analysis#Bit_vector_problems
 [*Static Program Analysis*]: https://cs.au.dk/~amoeller/spa/
-[Debugging MIR]: ./debugging.html
+[Debugging MIR]: ./debugging.md
 [`AnalysisDomain`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_mir_dataflow/trait.AnalysisDomain.html
 [`Analysis`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_mir_dataflow/trait.Analysis.html
 [`Engine`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_mir_dataflow/struct.Engine.html