| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2020-07-27 | mv std libs to library/ | mark | -267/+0 | |
| 2020-04-21 | Don't fuse Chain in its second iterator | Josh Stone | -10/+22 | |
| Only the "first" iterator is actually set `None` when exhausted, depending on whether you iterate forward or backward. This restores behavior similar to the former `ChainState`, where it would transition from `Both` to `Front`/`Back` and only continue from that side. However, if you mix directions, then this may still set both sides to `None`, totally fusing the iterator. | ||||
| 2020-04-07 | Avoid extra &mut in Chain::fold and try_fold | Josh Stone | -2/+2 | |
| 2020-04-07 | Reduce callsites in Chain::last() | Josh Stone | -11/+10 | |
| 2020-04-07 | Reduce callsites in Chain::count() | Josh Stone | -6/+9 | |
| 2020-04-07 | Implement Chain with Option fuses | Josh Stone | -149/+106 | |
| The iterators are now "fused" with `Option` so we don't need separate state to track which part is already exhausted, and we may also get niche layout for `None`. We don't use the real `Fuse` adapter because its specialization for `FusedIterator` unconditionally descends into the iterator, and that could be expensive to keep revisiting stuff like nested chains. It also hurts compiler performance to add more iterator layers to `Chain`. | ||||
| 2019-12-22 | Format the world | Mark Rousskov | -40/+47 | |
| 2019-11-01 | Fixed std::iter::Chain documentation | Oleg Nosov | -1/+1 | |
| 2019-08-18 | Fix bug in iter::Chain::size_hint | Tim Vermeulen | -8/+14 | |
| 2019-05-03 | Add custom nth_back for Chain | Andrea Corradi | -0/+23 | |
| 2019-04-22 | Remove double trailing newlines | varkor | -1/+0 | |
| 2019-04-18 | libcore => 2018 | Taiki Endo | -2/+3 | |
| 2019-01-22 | Don't expose ChainState to Iterator | Clar Fon | -4/+9 | |
| 2019-01-22 | Move Chain and ChainState to own module | Clar Fon | -0/+255 | |
