rust-ipfs/vendor/itertools
Vladislav Tsarev 3dec7eeb01 Initial commit
2024-10-18 11:36:33 +03:00
..
benches Initial commit 2024-10-18 11:36:33 +03:00
examples Initial commit 2024-10-18 11:36:33 +03:00
src Initial commit 2024-10-18 11:36:33 +03:00
tests Initial commit 2024-10-18 11:36:33 +03:00
.cargo-checksum.json Initial commit 2024-10-18 11:36:33 +03:00
Cargo.toml Initial commit 2024-10-18 11:36:33 +03:00
CHANGELOG.md Initial commit 2024-10-18 11:36:33 +03:00
clippy.toml Initial commit 2024-10-18 11:36:33 +03:00
LICENSE-APACHE Initial commit 2024-10-18 11:36:33 +03:00
LICENSE-MIT Initial commit 2024-10-18 11:36:33 +03:00
README.md Initial commit 2024-10-18 11:36:33 +03:00

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.