|
1 |
| - |
2 |
| -Itertools |
3 |
| -========= |
| 1 | +# Itertools |
4 | 2 |
|
5 | 3 | Extra iterator adaptors, functions and macros.
|
6 | 4 |
|
7 |
| -Please read the `API documentation here`__ |
8 |
| - |
9 |
| -__ https://docs.rs/itertools/ |
10 |
| - |
11 |
| -|build_status|_ |crates|_ |
| 5 | +Please read the [API documentation here](https://docs.rs/itertools/) |
12 | 6 |
|
13 |
| -.. |build_status| image:: https://travis-ci.org/rust-itertools/itertools.svg?branch=master |
14 |
| -.. _build_status: https://travis-ci.org/rust-itertools/itertools |
15 |
| - |
16 |
| -.. |crates| image:: https://meritbadge.herokuapp.com/itertools |
17 |
| -.. _crates: https://crates.io/crates/itertools |
| 7 | +[](https://travis-ci.org/rust-itertools/itertools) |
| 8 | +[](https://crates.io/crates/itertools) |
18 | 9 |
|
19 | 10 | How to use with cargo:
|
20 | 11 |
|
21 |
| -.. code:: toml |
22 |
| -
|
23 |
| - [dependencies] |
24 |
| - itertools = "0.10.0" |
| 12 | +``` |
| 13 | +[dependencies] |
| 14 | +itertools = "0.10.0" |
| 15 | +``` |
25 | 16 |
|
26 | 17 | How to use in your crate:
|
27 | 18 |
|
28 |
| -.. code:: rust |
29 |
| -
|
30 |
| - use itertools::Itertools; |
| 19 | +``` |
| 20 | +use itertools::Itertools; |
| 21 | +``` |
31 | 22 |
|
32 |
| -How to contribute |
33 |
| ------------------ |
| 23 | +## How to contribute |
34 | 24 |
|
35 | 25 | - Fix a bug or implement a new thing
|
36 | 26 | - Include tests for your new feature, preferably a quickcheck test
|
37 | 27 | - Make a Pull Request
|
38 | 28 |
|
39 |
| -For new features, please first consider filing a PR to `rust-lang/rust <https://github.com/rust-lang/rust>`_, |
| 29 | +For new features, please first consider filing a PR to [rust-lang/rust](https://github.com/rust-lang/rust), |
40 | 30 | adding your new feature to the `Iterator` trait of the standard library, if you believe it is reasonable.
|
41 | 31 | If it isn't accepted there, proposing it for inclusion in ``itertools`` is a good idea.
|
42 | 32 | The reason for doing is this is so that we avoid future breakage as with ``.flatten()``.
|
43 | 33 | However, if your feature involves heap allocation, such as storing elements in a ``Vec<T>``,
|
44 | 34 | then it can't be accepted into ``libcore``, and you should propose it for ``itertools`` directly instead.
|
45 | 35 |
|
46 |
| -License |
47 |
| -------- |
| 36 | +## License |
48 | 37 |
|
49 | 38 | Dual-licensed to be compatible with the Rust project.
|
50 | 39 |
|
|
0 commit comments