<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/compiler/rustc_data_structures/src/thin_vec/tests.rs, branch 1.56.0</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=1.56.0</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=1.56.0'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2021-04-06T02:09:51+00:00</updated>
<entry>
<title>Add `FromIterator` and `IntoIterator` impls for `ThinVec`</title>
<updated>2021-04-06T02:09:51+00:00</updated>
<author>
<name>Camelid</name>
<email>camelidcamel@gmail.com</email>
</author>
<published>2021-04-03T02:56:18+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=09ff88b600713a2bfca7cfdfd1828b519c907247'/>
<id>urn:sha1:09ff88b600713a2bfca7cfdfd1828b519c907247</id>
<content type='text'>
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`.
</content>
</entry>
</feed>
