Bug: 179100895

Clone this repo:
  1. ff6a718 Make itertools available to product and vendor am: 628255d06a am: 61f5aa6975 by Matthew Maurer · 7 months ago build-tools-release main master
  2. 61f5aa6 Make itertools available to product and vendor am: 628255d06a by Matthew Maurer · 7 months ago android-u-beta-1-gpl
  3. 628255d Make itertools available to product and vendor by Matthew Maurer · 7 months ago
  4. be203ff Update TEST_MAPPING am: 06b31b1da2 am: 5871dbacf1 by Jeff Vander Stoep · 8 months ago
  5. 5871dba Update TEST_MAPPING am: 06b31b1da2 by Jeff Vander Stoep · 8 months ago

Itertools

Extra iterator adaptors, functions and macros.

Please read the API documentation here.

build_status crates.io

How to use with Cargo:

[dependencies]
itertools = "0.10.5"

How to use in your crate:

use itertools::Itertools;

How to contribute

  • Fix a bug or implement a new thing
  • Include tests for your new feature, preferably a QuickCheck test
  • Make a Pull Request

For new features, please first consider filing a PR to rust-lang/rust, adding your new feature to the Iterator trait of the standard library, if you believe it is reasonable. If it isn‘t accepted there, proposing it for inclusion in itertools is a good idea. The reason for doing is this is so that we avoid future breakage as with .flatten(). However, if your feature involves heap allocation, such as storing elements in a Vec<T>, then it can’t be accepted into libcore, and you should propose it for itertools directly instead.

License

Dual-licensed to be compatible with the Rust project.

Licensed under the Apache License, Version 2.0 https://www.apache.org/licenses/LICENSE-2.0 or the MIT license https://opensource.org/licenses/MIT, at your option. This file may not be copied, modified, or distributed except according to those terms.