---

yaml
---
r: 229036
b: refs/heads/try
c: 14bc454
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: 06ded9c04e23ceaa41a4a5d01dd54432aaafd0db
+refs/heads/try: 14bc45477085222dcf2b87bef75ca3e7d0b5274a
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/try/src/doc/tarpl/vec-into-iter.md

@@ -51,22 +51,7 @@ struct IntoIter<T> {
 }
 ```
 
-One last subtle detail: if our Vec is empty, we want to produce an empty
-iterator. This will actually technically fall out doing the naive thing of:
-
-```text
-start = ptr
-end = ptr.offset(len)
-```
-
-However because `offset` is marked as a GEP inbounds instruction, this will tell
-LLVM that ptr is allocated and won't alias other allocated memory. This is fine
-for zero-sized types, as they can't alias anything. However if we're using
-`heap::EMPTY` as a sentinel for a non-allocation for a *non-zero-sized* type,
-this can cause Undefined Behaviour. Alas, we must therefore special case either
-cap or len being 0 to not do the offset.
-
-So this is what we end up with for initialization:
+And this is what we end up with for initialization:
 
 ```rust,ignore
 impl<T> Vec<T> {