---

yaml
---
r: 30337
b: refs/heads/incoming
c: 1c9c327
h: refs/heads/master
i:
  30335: 145ca46
v: v3

Author: pcwalton

[refs]

@@ -6,7 +6,7 @@ refs/heads/try: d324a424d8f84b1eb049b12cf34182bda91b0024
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
 refs/heads/try2: d0c6ce338884ee21843f4b40bf6bf18d222ce5df
-refs/heads/incoming: 69b363e02a29184641789598877409844736a7a1
+refs/heads/incoming: 1c9c32782d7dddadfbb9dd9dd149b33e28308439
 refs/heads/dist-snap: 2f32a1581f522e524009138b33b1c7049ced668d
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/incoming/doc/tutorial.md

@@ -1214,32 +1214,6 @@ let your_crayons = ~[banana_mania, beaver, bittersweet];
 my_crayons += your_crayons;
 ~~~~
 
-## Strings
-
-The `~str` type in Rust is represented exactly the same way as a unique
-vector of immutable bytes (`~[u8]`). This sequence of bytes is
-interpreted as an UTF-8 encoded sequence of characters. This has the
-advantage that UTF-8 encoded I/O (which should really be the default
-for modern systems) is very fast, and that strings have, for most
-intents and purposes, a nicely compact representation. It has the
-disadvantage that you only get constant-time access by byte, not by
-character.
-
-~~~~
-let huh = ~"what?";
-let que: u8 = huh[4]; // indexing a string returns a `u8`
-assert que == '?' as u8;
-~~~~
-
-A lot of algorithms don't need constant-time indexed access (they
-iterate over all characters, which `str::chars` helps with), and
-for those that do, many don't need actual characters, and can operate
-on bytes. For algorithms that do really need to index by character,
-there are core library functions available.
-
-> ***Note:*** like vectors, strings will soon be allocatable in
-> the local heap and on the stack, in addition to the exchange heap.
-
 ## Vector and string methods
 
 Both vectors and strings support a number of useful