---

yaml
---
r: 27904
b: refs/heads/try
c: 1d3abf1
h: refs/heads/master
v: v3

Author: catamorphism

[refs]

@@ -2,7 +2,7 @@
 refs/heads/master: cd6f24f9d14ac90d167386a56e7a6ac1f0318195
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: cd6f24f9d14ac90d167386a56e7a6ac1f0318195
-refs/heads/try: 3e52a0acdec93357806771eb04f0f479873a637b
+refs/heads/try: 1d3abf15f149036cfd0fa939f6393136ffcd1d7f
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
 refs/heads/try2: d0c6ce338884ee21843f4b40bf6bf18d222ce5df

branches/try/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