| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2017-09-22 | Add support for `..=` syntax | Alex Burka | -14/+14 | |
| Add ..= to the parser Add ..= to libproc_macro Add ..= to ICH Highlight ..= in rustdoc Update impl Debug for RangeInclusive to ..= Replace `...` to `..=` in range docs Make the dotdoteq warning point to the ... Add warning for ... in expressions Updated more tests to the ..= syntax Updated even more tests to the ..= syntax Updated the inclusive_range entry in unstable book | ||||
| 2017-07-19 | Add Vec::drain_filter | Alexis Beingessner | -0/+167 | |
| 2017-07-03 | Document unintuitive argument order for Vec::dedup_by relation | Anders Kaseorg | -0/+5 | |
| When trying to use dedup_by to merge some auxiliary information from removed elements into kept elements, I was surprised to observe that vec.dedup_by(same_bucket) calls same_bucket(a, b) where b appears before a in the vector, and discards a when true is returned. This argument order is probably a bug, but since it has already been stabilized, I guess we should document it as a feature and move on. (Vec::dedup also uses == with this unexpected argument order, but I figure that’s not important since == is expected to be symmetric with no side effects.) Signed-off-by: Anders Kaseorg <andersk@mit.edu> | ||||
| 2017-06-13 | Merge crate `collections` into `alloc` | Murarth | -0/+798 | |
