---

yaml
---
r: 210364
b: refs/heads/try
c: 414dfb1
h: refs/heads/master
v: v3

Author: ruuda

[refs]

@@ -2,7 +2,7 @@
 refs/heads/master: 3e561f05c00cd180ec02db4ccab2840a4aba93d2
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: ba0e1cd8147d452c356aacb29fb87568ca26f111
-refs/heads/try: 6b292cd4c48f0876b4280dfdf0c38d474fe44330
+refs/heads/try: 414dfb13df96a373c7fd37f6beb299e176675e0e
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/dist-snap: ba4081a5a8573875fed17545846f6f6902c8ba8d
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596

branches/try/src/librustc/diagnostics.rs

@@ -375,39 +375,40 @@ by adding a type annotation. Sometimes you need to specify a generic type
 parameter manually.
 
 A common example is the `collect` method on `Iterator`. It has a generic type
-parameter with a `FromIterator` bound, which is implemented by `Vec` and
-`VecDeque` among others. Consider the following snippet:
+parameter with a `FromIterator` bound, which for a `char` iterator is
+implemented by `Vec` and `String` among others. Consider the following snippet
+that reverses the characters of a string:
 
 ```
-let x = (1_i32 .. 10).collect();
+let x = "hello".chars().rev().collect();
 ```
 
 In this case, the compiler cannot infer what the type of `x` should be:
-`Vec<i32>` and `VecDeque<i32>` are both suitable candidates. To specify which
-type to use, you can use a type annotation on `x`:
+`Vec<char>` and `String` are both suitable candidates. To specify which type to
+use, you can use a type annotation on `x`:
 
 ```
-let x: Vec<i32> = (1_i32 .. 10).collect();
+let x: Vec<char> = "hello".chars().rev().collect();
 ```
 
-It is not necessary to annotate the full type, once the ambiguity is resolved,
+It is not necessary to annotate the full type. Once the ambiguity is resolved,
 the compiler can infer the rest:
 
 ```
-let x: Vec<_> = (1_i32 .. 10).collect();
+let x: Vec<_> = "hello".chars().rev().collect();
 ```
 
 Another way to provide the compiler with enough information, is to specify the
 generic type parameter:
 
 ```
-let x = (1_i32 .. 10).collect::<Vec<i32>>();
+let x = "hello".chars().rev().collect::<Vec<char>>();
 ```
 
 Again, you need not specify the full type if the compiler can infer it:
 
 ```
-let x = (1_i32 .. 10).collect::<Vec<_>>();
+let x = "hello".chars().rev().collect::<Vec<_>>();
 ```
 
 Apart from a method or function with a generic type parameter, this error can