diff options
| author | Dylan DPC <dylan.dpc@gmail.com> | 2020-11-09 19:06:39 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-11-09 19:06:39 +0100 |
| commit | 99f16e637b47fb9de3b88e8df6dbc68be180cd96 (patch) | |
| tree | 2616a6a3e193f700edd985e1d9511bac73fe2eeb /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | 46bce9f8efbd4c57a23e822588650250d1e74b26 (diff) | |
| parent | 61b52a33b3a5a170f7760ba3e3efaac25e5085ef (diff) | |
| download | rust-99f16e637b47fb9de3b88e8df6dbc68be180cd96.tar.gz rust-99f16e637b47fb9de3b88e8df6dbc68be180cd96.zip | |
Rollup merge of #76468 - SNCPlay42:lifetime-names, r=Mark-Simulacrum
Improve lifetime name annotations for closures & async functions * Don't refer to async functions as "generators" in error output * Where possible, emit annotations pointing exactly at the `&` in the return type of closures (when they have explicit return types) and async functions, like we do for arguments. Addresses #74072, but I wouldn't call that *closed* until annotations are identical for async and non-async functions. * Emit a better annotation when the lifetime doesn't appear in the full name type, which currently happens for opaque types like `impl Future`. Addresses #74497, but further improves could probably be made (why *doesn't* it appear in the type as `impl Future + '1`?) This is included in the same PR because the changes to `give_name_if_anonymous_region_appears_in_output` would introduce ICE otherwise (it would return `None` in cases where it didn't previously, which then gets `unwrap`ped)
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
