---

yaml
---
r: 229038
b: refs/heads/try
c: 3f8e029
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: 5f02de3c226bce60c58ce2bc436e69c55b90a616
+refs/heads/try: 3f8e029bedba23b8b2d174fac2718f970a396676
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/try/src/doc/tarpl/coercions.md

@@ -1,16 +1,16 @@
 % Coercions
 
 Types can implicitly be coerced to change in certain contexts. These changes are
-generally just *weakening* of types, largely focused around pointers and lifetimes.
-They mostly exist to make Rust "just work" in more cases, and are largely harmless.
+generally just *weakening* of types, largely focused around pointers and
+lifetimes. They mostly exist to make Rust "just work" in more cases, and are
+largely harmless.
 
 Here's all the kinds of coercion:
 
-
 Coercion is allowed between the following types:
 
-* Subtyping: `T` to `U` if `T` is a [subtype][] of `U`
-* Transitivity: `T_1` to `T_3` where `T_1` coerces to `T_2` and `T_2` coerces to `T_3`
+* Transitivity: `T_1` to `T_3` where `T_1` coerces to `T_2` and `T_2` coerces to
+  `T_3`
 * Pointer Weakening:
     * `&mut T` to `&T`
     * `*mut T` to `*const T`
@@ -68,5 +68,3 @@ fn main() {
 <anon>:10     foo(t);
               ^~~
 ```
-
-[subtype]: subtyping.html