diff options
| author | bors <bors@rust-lang.org> | 2021-08-14 07:01:36 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2021-08-14 07:01:36 +0000 |
| commit | 99efc51dae1dbe9d741707a7ddef84c29e654df5 (patch) | |
| tree | 19a98d216296a5b00b034678949d238b62bcb004 /src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs | |
| parent | c6094fc7b9981d755abeb8c0e866a0f6315b3ec3 (diff) | |
| parent | cf5eda1b4d24d508039e96d939043268e955af6f (diff) | |
| download | rust-99efc51dae1dbe9d741707a7ddef84c29e654df5.tar.gz rust-99efc51dae1dbe9d741707a7ddef84c29e654df5.zip | |
Auto merge of #85020 - lrh2000:named-upvars, r=tmandry
Name the captured upvars for closures/generators in debuginfo
Previously, debuggers print closures as something like
```
y::main::closure-0 (0x7fffffffdd34)
```
The pointer actually references to an upvar. It is not very obvious, especially for beginners.
It's because upvars don't have names before, as they are packed into a tuple. This PR names the upvars, so we can expect to see something like
```
y::main::closure-0 {_captured_ref__b: 0x[...]}
```
r? `@tmandry`
Discussed at https://github.com/rust-lang/rust/pull/84752#issuecomment-831639489 .
Diffstat (limited to 'src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs')
0 files changed, 0 insertions, 0 deletions