about summary refs log tree commit diff
path: root/compiler/rustc_codegen_gcc/example/example.rs
diff options
context:
space:
mode:
authorDylan DPC <99973273+Dylan-DPC@users.noreply.github.com>2022-03-31 00:26:30 +0200
committerGitHub <noreply@github.com>2022-03-31 00:26:30 +0200
commit1c3657b20d9dc52574bcd19876ed56e1538bd605 (patch)
tree0f54e622c3299a6aafc233e29b73fc188983de9b /compiler/rustc_codegen_gcc/example/example.rs
parente08ab08a2e8c470d62aa7d41b1c1dc42696f9da8 (diff)
parent78e27e2c7a85021a0b72253c17d0d99a383e8385 (diff)
downloadrust-1c3657b20d9dc52574bcd19876ed56e1538bd605.tar.gz
rust-1c3657b20d9dc52574bcd19876ed56e1538bd605.zip
Rollup merge of #95011 - michaelwoerister:awaitee_field, r=tmandry
async: Give predictable name to binding generated from .await expressions.

This name makes it to debuginfo and allows debuggers to identify such bindings and their captured versions in suspended async fns.

This will be useful for async stack traces, as discussed in https://internals.rust-lang.org/t/async-debugging-logical-stack-traces-setting-goals-collecting-examples/15547.

I don't know if this needs some discussion by ````@rust-lang/compiler,```` e.g. about the name of the binding (`__awaitee`) or about the fact that this PR introduces a (soft) guarantee about a compiler generated name. Although, regarding the later, I think the same reasoning applies here as it does for debuginfo in general.

r? ````@tmandry````
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/example.rs')
0 files changed, 0 insertions, 0 deletions