Skip to content

Commit 4c3802d

Browse files
authored
Rollup merge of rust-lang#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 rust-lang#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
2 parents cf8da0a + bd18dba commit 4c3802d

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

alloc/src/collections/btree/node.rs

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,6 @@ impl<K, V> LeafNode<K, V> {
8787
#[repr(C)]
8888
// gdb_providers.py uses this type name for introspection.
8989
struct InternalNode<K, V> {
90-
// gdb_providers.py uses this field name for introspection.
9190
data: LeafNode<K, V>,
9291

9392
/// The pointers to the children of this node. `len + 1` of these are considered

0 commit comments

Comments
 (0)