about summary refs log tree commit diff
path: root/compiler/rustc_codegen_gcc
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2022-01-11 14:23:24 +0000
committerbors <bors@rust-lang.org>2022-01-11 14:23:24 +0000
commit2e2c86eba21a08cf505cd67073736d03ff3887ad (patch)
treea70d28fe023540384d2ab9153708bec5b5e8ed06 /compiler/rustc_codegen_gcc
parente4b1d5841494d6eb7f4944c91a057e16b0f0a9ea (diff)
parent08829853d3c69f68a5a09fb4bcc53ca87d373a78 (diff)
downloadrust-2e2c86eba21a08cf505cd67073736d03ff3887ad.tar.gz
rust-2e2c86eba21a08cf505cd67073736d03ff3887ad.zip
Auto merge of #92070 - rukai:replace_vec_into_iter_with_array_into_iter, r=Mark-Simulacrum
Replace usages of vec![].into_iter with [].into_iter

`[].into_iter` is idiomatic over `vec![].into_iter` because its simpler and faster (unless the vec is optimized away in which case it would be the same)

So we should change all the implementation, documentation and tests to use it.

I skipped:
* `src/tools` - Those are copied in from upstream
* `src/test/ui` - Hard to tell if `vec![].into_iter` was used intentionally or not here and not much benefit to changing it.
*  any case where `vec![].into_iter` was used because we specifically needed a `Vec::IntoIter<T>`
*  any case where it looked like we were intentionally using `vec![].into_iter` to test it.
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions