https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=master 2022-08-29T05:42:13+00:00 2022-08-29T05:42:13+00:00 Nicholas Nethercote n.nethercote@gmail.com 2022-08-17T04:22:30+00:00 urn:sha1:b38106b6d8478fbfbded5403ee31c056c71cef48 `rustc_data_structures::thin_vec::ThinVec` looks like this: ``` pub struct ThinVec<T>(Option<Box<Vec<T>>>); ``` It's just a zero word if the vector is empty, but requires two allocations if it is non-empty. So it's only usable in cases where the vector is empty most of the time. This commit removes it in favour of `thin_vec::ThinVec`, which is also word-sized, but stores the length and capacity in the same allocation as the elements. It's good in a wider variety of situation, e.g. in enum variants where the vector is usually/always non-empty. The commit also: - Sorts some `Cargo.toml` dependency lists, to make additions easier. - Sorts some `use` item lists, to make additions easier. - Changes `clean_trait_ref_with_bindings` to take a `ThinVec<TypeBinding>` rather than a `&[TypeBinding]`, because this avoid some unnecessary allocations. 2022-01-09T03:09:25+00:00 Lucas Kent rubickent@gmail.com 2021-12-17T07:36:18+00:00 urn:sha1:08829853d3c69f68a5a09fb4bcc53ca87d373a78 2021-04-06T02:09:51+00:00 Camelid camelidcamel@gmail.com 2021-04-03T02:56:18+00:00 urn:sha1:09ff88b600713a2bfca7cfdfd1828b519c907247 These should make using `ThinVec` feel much more like using `Vec`. They will allow users of `Vec` to switch to `ThinVec` while continuing to use `collect()`, `for` loops, and other parts of the iterator API. I don't know if there were use cases before for using the iterator API with `ThinVec`, but I would like to start using `ThinVec` in rustdoc, and having it conform to the iterator API would make the transition *a lot* easier. I added a `FromIterator` impl, an `IntoIterator` impl that yields owned elements, and `IntoIterator` impls that yield immutable or mutable references to elements. I also added some unit tests for `ThinVec`.