-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Replace internal iteration functions in std::either and std::result #8228
Comments
I'm working on it |
Can't find any internal iteration functions in |
working on replacing some of the rest of the functions.. not internal iterators, but vector -> vector functions. |
bors
added a commit
that referenced
this issue
Aug 16, 2013
Retry of PR #8471 Replace the remaining functions marked for issue #8228 with similar functions that are iterator-based. Change `either::{lefts, rights}` to be iterator-filtering instead of returning a vector. Replace `map_vec`, `map_vec2`, `iter_vec2` in std::result with three functions: * `result::collect` gathers `Iterator<Result<V, U>>` to `Result<~[V], U>` * `result::fold` folds `Iterator<Result<T, E>>` to `Result<V, E>` * `result::fold_` folds `Iterator<Result<T, E>>` to `Result<(), E>`
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Jan 13, 2022
…5, r=giraffate fix `iter_not_returning_iterator` fixes rust-lang#8225 changelog: Handle type projections in `iter_not_returning_iterator` changelog: Don't lint `iter_not_returning_iterator` in trait implementations changelog: Lint `iter_not_returning_iterator` in trait definitions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Either
andResult
currently define a bunch of internal iteration functions.Where applicable, those should be replaced by external iterators.
The text was updated successfully, but these errors were encountered: