---

yaml
---
r: 229028
b: refs/heads/try
c: 13b2605
h: refs/heads/master
v: v3

Author: Gankra

[refs]

@@ -1,7 +1,7 @@
 ---
 refs/heads/master: aca2057ed5fb7af3f8905b2bc01f72fa001c35c8
 refs/heads/snap-stage3: 1af31d4974e33027a68126fa5a5a3c2c6491824f
-refs/heads/try: c97673c7b0fffe131822f2a5be520cf408c68319
+refs/heads/try: 13b2605ed985a37481dc497357dc6dcdf37ba6ff
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/try/src/doc/tarpl/checked-uninit.md

@@ -68,6 +68,29 @@ fn main() {
 }
 ```
 
+Of course, while the analysis doesn't consider actual values, it does
+have a relatively sophisticated understanding of dependencies and control
+flow. For instance, this works:
+
+```rust
+let x: i32;
+
+loop {
+    // Rust doesn't understand that this branch will be taken unconditionally,
+    // because it relies on actual values.
+    if true {
+        // But it does understand that it will only be taken once because
+        // we *do* unconditionally break out of it. Therefore `x` doesn't
+        // need to be marked as mutable.
+        x = 0;
+        break;
+    }
+}
+// It also knows that it's impossible to get here without reaching the break.
+// And therefore that `x` must be initialized here!
+println!("{}", x);
+```
+
 If a value is moved out of a variable, that variable becomes logically
 uninitialized if the type of the value isn't Copy. That is:
 

branches/try/src/doc/tarpl/other-reprs.md

@@ -47,7 +47,7 @@ discriminant.
 On non-C-like enums, this will inhibit certain optimizations like the null-
 pointer optimization.
 
-These reprs have no affect on a struct.
+These reprs have no effect on a struct.