about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2024-01-26 06:36:39 +0100
committerGitHub <noreply@github.com>2024-01-26 06:36:39 +0100
commite4003114860fef6d2eaa56c394dbfe7e4bff0db2 (patch)
treeaa83abea2ffd9c72cf431ba78cfc889d2fcb71a0 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
parent626797b61db2467e4c6e8f5f180130e94d50c964 (diff)
parent8c2ae804e386d0e8e49233d23ce35469316eea52 (diff)
downloadrust-e4003114860fef6d2eaa56c394dbfe7e4bff0db2.tar.gz
rust-e4003114860fef6d2eaa56c394dbfe7e4bff0db2.zip
Rollup merge of #120322 - compiler-errors:higher-ranked-async-closures, r=oli-obk
Don't manually resolve async closures in `rustc_resolve`

There's a comment here that talks about doing this "[so] closure [args] are detected as upvars rather than normal closure arg usages", but we do upvar analysis on the HIR now:

https://github.com/rust-lang/rust/blob/cd6d8f2a04528f827ad3d399581c0f3502b15a72/compiler/rustc_passes/src/upvars.rs#L21-L29

Removing this ad-hoc logic makes it so that `async |x: &str|` now introduces an implicit binder, like regular closures.

r? ```@oli-obk```
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions