Skip to content

Iterator::cloned: document side effect behavior #92543

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions library/core/src/iter/traits/iterator.rs
Original file line number Diff line number Diff line change
Expand Up @@ -2998,6 +2998,11 @@ pub trait Iterator {
/// This is useful when you have an iterator over `&T`, but you need an
/// iterator over `T`.
///
/// Note that unlike copying, cloning is regarded as a side effect, because
/// `Clone` implementations may contain observable behavior. For example,
/// `iter.cloned().last()` will clone all elements even if only the last
/// one is actually returned.
///
/// [`clone`]: Clone::clone
///
/// # Examples
Expand Down