Update TEST_MAPPING

Test: atest
Change-Id: I5693147b09c443a131d97edc756c2b25161a4c91
1 file changed
tree: 6634ac30dc6636eb209a3c7dcc701beb7766cebe
  1. .github/
  2. benches/
  3. examples/
  4. src/
  5. tests/
  6. .cargo_vcs_info.json
  7. .gitignore
  8. .rustfmt.toml
  9. Android.bp
  10. Cargo.toml
  11. Cargo.toml.orig
  12. cargo2android.json
  13. CHANGELOG.md
  14. clippy.toml
  15. LICENSE-APACHE
  16. LICENSE-MIT
  17. METADATA
  18. MODULE_LICENSE_APACHE2
  19. OWNERS
  20. README.md
  21. TEST_MAPPING
README.md

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.