about summary refs log tree commit diff
path: root/src/rustllvm/RustWrapper.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2018-09-30 09:22:31 +0000
committerbors <bors@rust-lang.org>2018-09-30 09:22:31 +0000
commita677e4c347630b855f2889557c2d37180a1a41be (patch)
tree9be1a07b23cc39e61071592e0c156d29fe668b71 /src/rustllvm/RustWrapper.cpp
parent8c1d5e5b712fa372d5dcab5a5bb97b24a6a7fef3 (diff)
parent5b22d9b2ca68bd3fc14613d355ffad21a1cb7899 (diff)
downloadrust-a677e4c347630b855f2889557c2d37180a1a41be.tar.gz
rust-a677e4c347630b855f2889557c2d37180a1a41be.zip
Auto merge of #53816 - zackmdavis:elided_lifetimes_in_paths_field_day, r=nikomatsakis
don't elide lifetimes in paths in librustc/

In light of the "Apply to rustc" checkbox on #44524 and @nikomatsakis's [recent comment about regularly wanting visual indication of elided lifetimes in types](https://github.com/rust-lang/rust/issues/44524#issuecomment-414663773), I was curious to see what it would look like if we turned the `elided_lifetimes_in_path` lint on in at least one crate in the codebase (I chose librustc). Given that I couldn't figure out how to get `cargo fix` work with the build system, this arguably wasn't a very efficient use of my time, but once I started, the conjunction of moral law and the sunk cost fallacy forced me to continue.

This is mostly applying the `<'_>` suggestions issued by the lint, but there were a few places where I named the lifetimes (_e.g._, `<'a, 'gcx, 'tcx>` on `TyCtxt`) in order to match style with surrounding code.

r? @nikomatsakis
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions