diff options
| author | bors <bors@rust-lang.org> | 2016-08-23 07:46:52 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-08-23 07:46:52 -0700 |
| commit | 0bd99f9d5c3bb10920f33819b38392137f7bfa11 (patch) | |
| tree | c4ab1e85690bc75a19094186ed62cbed6ef3eaca /src/rustllvm/RustWrapper.cpp | |
| parent | 43204fff5d0a656f8a94bfff3129e04bc9d30ad4 (diff) | |
| parent | de91872a3337dddf9a0d27df7bfb64f3965c81b0 (diff) | |
| download | rust-0bd99f9d5c3bb10920f33819b38392137f7bfa11.tar.gz rust-0bd99f9d5c3bb10920f33819b38392137f7bfa11.zip | |
Auto merge of #35656 - Stebalien:fused, r=alexcrichton
Implement 1581 (FusedIterator)
* [ ] Implement on patterns. See https://github.com/rust-lang/rust/issues/27721#issuecomment-239638642.
* [ ] Handle OS Iterators. A bunch of iterators (`Args`, `Env`, etc.) in libstd wrap platform specific iterators. The current ones all appear to be well-behaved but can we assume that future ones will be?
* [ ] Does someone want to audit this? On first glance, all of the iterators on which I implemented `FusedIterator` appear to be well-behaved but there are a *lot* of them so a second pair of eyes would be nice.
* I haven't touched rustc internal iterators (or the internal rand) because rustc doesn't actually call `fuse()`.
* `FusedIterator` can't be implemented on `std::io::{Bytes, Chars}`.
Closes: #35602 (Tracking Issue)
Implements: rust-lang/rfcs#1581
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions