Inconsistent hex representation of typed constants with unsigned int type

[corneliusweig]

1. What version of Delve are you using (dlv version)? 1.21.0
2. What version of Go are you using? (go version)? 1.21
3. What operating system and processor architecture are you using? Linux
4. What did you do? Debug the following program in VS Code, using Delve's DAP adapter:

package main

import "fmt"

type A uint32

const (
	zero = A(iota)
	one
	two
)

func main() {
	a := zero
	b := one
	c := two
	d := A(3)
	e := A(4)
	fmt.Println(a, b, c, d, e)  // halt here
}

In particular, the program defines a new type with an underlying unsigned int type and a few constants of that type.

8. What did you see instead?

The hex representation of values of type A is inconsistent with the numeric value. This only happens for unsigned int types, and as long as the value can be represented as a binary OR of predefined constants of that type:

The expected representation should be:

a: zero (0) = 0x0
b: one (1) = 0x1
c: two (2) = 0x2
d: one|two (3) = 0x3
e: 4 = 0x4

[corneliusweig]

Thank you for this awesomely quick fix!