---

thestinger · thestinger · commit 6d95455301c8 · 2014-10-28T19:00:16.000-04:00
yaml --- r: 157208 b: refs/heads/master c: 8a71925 h: refs/heads/master v: v3
diff --git a/[refs] b/[refs]
@@ -1,5 +1,5 @@
 ---
-refs/heads/master: 768a7e1a4a891191f3653cebc223dfad0e8b875c
+refs/heads/master: 8a719255589bcbc82c961e051f09678b524f4149
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: d44ea720fa9dfe062ef06d0eb49a58d4e7e92344
 refs/heads/try: 6ecdf1fa83d7cdbf44a0091132e9c6580be72275
diff --git a/trunk/src/doc/reference.md b/trunk/src/doc/reference.md
@@ -1170,6 +1170,9 @@ exposing an API making it possible for it to occur in safe code.
   * A discriminant in an `enum` not included in the type definition
   * A value in a `char` which is a surrogate or above `char::MAX`
   * non-UTF-8 byte sequences in a `str`
+* Unwinding into Rust from foreign code or unwinding from Rust into foreign
+  code. Rust's failure system is not compatible with exception handling in
+  other languages. Unwinding must be caught and handled at FFI boundaries.
 
 ##### Behaviour not considered unsafe
 
