diff options
| author | bors <bors@rust-lang.org> | 2015-04-13 12:39:49 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2015-04-13 12:39:49 +0000 |
| commit | b9ed9e2a326cafa6f2445aec7221dc419089cf5f (patch) | |
| tree | 9163f199f70e5b84c88c86dd08d4b64851702c8d /src/libstd/sys/unix/ext.rs | |
| parent | 3cac76bcf239c5db7d612eea52dd39be6e0281b4 (diff) | |
| parent | 03f92694966259ee156bb8f3a7ef9d4dc587ecb9 (diff) | |
| download | rust-b9ed9e2a326cafa6f2445aec7221dc419089cf5f.tar.gz rust-b9ed9e2a326cafa6f2445aec7221dc419089cf5f.zip | |
Auto merge of #24351 - michaelwoerister:named-tuple-fields, r=alexcrichton
This PR makes `rustc` emit field names for tuple fields in DWARF. Formerly there was no way of directly accessing the fields of a tuple in GDB and LLDB since there is no C/C++ equivalent to this. Now, the debugger sees the name `__{field-index}` for tuple fields. So you can type for example `some_tuple_val.__2` to get the third tuple component.
When pretty printers are used (e.g. via `rust-gdb` or `rust-lldb`) these artificial field names will not clutter tuple rendering (which was the main motivation for not doing this in the past).
Solves #21948.
Diffstat (limited to 'src/libstd/sys/unix/ext.rs')
0 files changed, 0 insertions, 0 deletions