---

yaml
---
r: 275727
b: refs/heads/master
c: 322f3a3
h: refs/heads/master
i:
  275725: f30fb2d
  275723: e39baa7
  275719: 0611bee
  275711: d044d52

Author: tamird

[refs]

@@ -1,5 +1,5 @@
 ---
-refs/heads/master: 253b7c1e1a919a6b722c29a04241d6f08ff8c79a
+refs/heads/master: 322f3a3eaac6cbaa3b1e85bca0402d0ff2b6779f
 refs/heads/snap-stage3: 235d77457d80b549dad3ac36d94f235208a1eafb
 refs/heads/try: 49312a405e14a449b98fe0056b12a40ac128be4a
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105

trunk/src/doc/book/const-and-static.md

@@ -79,5 +79,5 @@ the result of a function call or anything similarly complex or at runtime.
 
 Almost always, if you can choose between the two, choose `const`. It’s pretty
 rare that you actually want a memory location associated with your constant,
-and using a `const` allows for optimizations like constant propagation not only
+and using a const allows for optimizations like constant propagation not only
 in your crate but downstream crates.

trunk/src/libcore/iter/iterator.rs

@@ -598,13 +598,13 @@ pub trait Iterator {
     /// # Examples
     ///
     /// ```
-    /// let a = ['a', 'b', 'c'];
+    /// let a = [1, 2, 3];
     ///
     /// let mut iter = a.iter().enumerate();
     ///
-    /// assert_eq!(iter.next(), Some((0, &'a')));
-    /// assert_eq!(iter.next(), Some((1, &'b')));
-    /// assert_eq!(iter.next(), Some((2, &'c')));
+    /// assert_eq!(iter.next(), Some((0, &1)));
+    /// assert_eq!(iter.next(), Some((1, &2)));
+    /// assert_eq!(iter.next(), Some((2, &3)));
     /// assert_eq!(iter.next(), None);
     /// ```
     #[inline]
@@ -2109,3 +2109,4 @@ impl<'a, I: Iterator + ?Sized> Iterator for &'a mut I {
     fn next(&mut self) -> Option<I::Item> { (**self).next() }
     fn size_hint(&self) -> (usize, Option<usize>) { (**self).size_hint() }
 }
+