---

yaml
---
r: 29926
b: refs/heads/incoming
c: 1d3abf1
h: refs/heads/master
v: v3

Author: catamorphism

[refs]

@@ -6,7 +6,7 @@ refs/heads/try: d324a424d8f84b1eb049b12cf34182bda91b0024
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
 refs/heads/try2: d0c6ce338884ee21843f4b40bf6bf18d222ce5df
-refs/heads/incoming: 3e52a0acdec93357806771eb04f0f479873a637b
+refs/heads/incoming: 1d3abf15f149036cfd0fa939f6393136ffcd1d7f
 refs/heads/dist-snap: 2f32a1581f522e524009138b33b1c7049ced668d
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/incoming/doc/tutorial.md

@@ -1859,6 +1859,13 @@ match my_rec {
 }
 ~~~~
 
+It's unsafe to dereference `b` in the second `log` expression, because `b` is
+a _pointer_ to the inside of `my_rec`, and the assignment statement has
+allocated a new record and assigned `my_rec` to point to it. Thus, the old
+contents of `my_rec` are no longer live, and `b` is dangling at this point.
+The borrow-checking analysis inside the compiler recognizes this situation
+and rejects the program.
+
 ## Argument passing styles
 
 The fact that arguments are conceptually passed by safe reference does