]> git.lizzy.rs Git - rust.git/commit
projects / rust.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(merge: e02d645 bbdff1f)
Auto merge of #93700 - rossmacarthur:ft/iter-next-chunk, r=m-ou-se
authorbors <bors@rust-lang.org>
Sat, 25 Jun 2022 09:40:54 +0000 (09:40 +0000)
committerbors <bors@rust-lang.org>
Sat, 25 Jun 2022 09:40:54 +0000 (09:40 +0000)
commit1aabd8a4a6e1871f14e804302bd60dfcbffd5761
tree12bcc9025a321d57a1007b5ed053bd4811724a29tree | snapshot
parente02d645110ae14f4a7f04d6bd5b05f2842488ddacommit | diff
parentbbdff1fff49a6f816aa35d9b84c79b2603f0961bcommit | diff
Auto merge of #93700 - rossmacarthur:ft/iter-next-chunk, r=m-ou-se

Add `Iterator::next_chunk`

See also https://github.com/rust-lang/rust/pull/92393

### Prior art

-  [`Itertools::next_tuple()`](https://docs.rs/itertools/latest/itertools/trait.Itertools.html#method.next_tuple)

### Unresolved questions

- Should we also add `next_chunk_back` to `DoubleEndedIterator`?
- Should we rather call this `next_array()` or `next_array_chunk`?
Empowering everyone to build reliable and efficient software.