nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2025-04-11 19:46:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Rollup merge of - rust-lang:opt-fuse, r=shepmaster

Browse Source 
Document optimizations enabled by FusedIterator

When reading this I wondered what “some significant optimizations” referred to. As far as I can tell from reading code, the specialization of `.fuse()` is the only case where `FusedIterator` has any impact at all. Is this accurate @Stebalien?
This commit is contained in:
kennytm 2018-11-13 13:03:24 +08:00
commit 4d764407e9
No known key found for this signature in database
GPG Key ID: FEF6C8051D0E013C
1 changed files with 1 additions and 1 deletions

2
src/libcore/iter/traits.rs
View File

@ -960,7 +960,7 @@ impl<T, U, E> Product<Result<U, E>> for Result<T, E>
///
/// Calling next on a fused iterator that has returned `None` once is guaranteed
/// to return [`None`] again. This trait should be implemented by all iterators
/// that behave this way because it allows for some significant optimizations.
/// that behave this way because it allows optimizing [`Iterator::fuse`].
///
/// Note: In general, you should not use `FusedIterator` in generic bounds if
/// you need a fused iterator. Instead, you should just call [`Iterator::fuse`]