diff options
| author | Dylan DPC <dylan.dpc@gmail.com> | 2020-10-17 03:27:18 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-10-17 03:27:18 +0200 |
| commit | 16b878fd0fff7bcd69cbecf692e71281fe0117a7 (patch) | |
| tree | 66526c908b92b8a0808fee515c02dc04d4e3e27b /compiler/rustc_codegen_llvm/src | |
| parent | 446686f59b9f9d63ede5e8a07a7298c43209e651 (diff) | |
| parent | 28af355b9ffa7fdd1761caa4dd323eacd68ee0ed (diff) | |
| download | rust-16b878fd0fff7bcd69cbecf692e71281fe0117a7.tar.gz rust-16b878fd0fff7bcd69cbecf692e71281fe0117a7.zip | |
Rollup merge of #77932 - ssomers:btree_cleanup_gdb, r=Mark-Simulacrum
BTreeMap: improve gdb introspection of BTreeMap with ZST keys or values
I accidentally pushed an earlier revision in #77788: it changes the index of tuples for BTreeSet from ""[{}]".format(i) to "key{}".format(i). Which doesn't seem to make the slightest difference on my linux box nor on CI. In fact, gdb doesn't make any distinction between "key{}" and "val{}" for a BTreeMap either, leading to confusing output if you test more. But easy to improve.
r? @Mark-Simulacrum
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions