diff options
| author | bors <bors@rust-lang.org> | 2021-12-06 09:58:57 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2021-12-06 09:58:57 +0000 |
| commit | bc9326d83d0d8368057ca8ff21c5260a4286f7ab (patch) | |
| tree | c09ad69463a5ec3549e015ffef6666f72f8b4189 /compiler/rustc_codegen_gcc | |
| parent | ba9fc4fbfe1ea33271d68c2ee6bd8f5a54197a75 (diff) | |
| parent | 308fd59f42dff89e55dff1c7a85fa9fa2411cab3 (diff) | |
| download | rust-bc9326d83d0d8368057ca8ff21c5260a4286f7ab.tar.gz rust-bc9326d83d0d8368057ca8ff21c5260a4286f7ab.zip | |
Auto merge of #91580 - scottmcm:less-inband-1-of-28, r=petrochenkov
Stop enabling `in_band_lifetimes` in rustc_data_structures There's a conversation started in the tracking issue about possibly unaccepting `in_band_lifetimes`, but it's used heavily in the compiler, and thus there'd need to be a bunch of PRs like this if that were to happen. So here's one to see how much of an impact it has. For this crate, at least, it doesn't seem like in-band was a big win -- about half the places that were using it didn't even need a named lifetime. (Oh, and I removed `nll` while I was here too, since it didn't seem needed. Let me know if I should put that back.) r? `@petrochenkov`
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions
