I don't think this is a bug. Confusing, I agree, but it follows the spec for composite literals.

It is an error to specify multiple elements with the same field name or constant key value. For non-constant map keys, see the section on evaluation order.

The crux of the question is whether the key you are using is a constant. https://go.dev/ref/spec#Constants lists the constants, and structs (empty or otherwise) are not constants. Even if they are obviously constant to you and me, they are not "Go constants" according to the spec.

For non-constants, we run each entry in the literal as an insert, in program order. There's no error possible in that scenario, we just get subsequent keys overwriting previous ones. That's why you get {}:2 at the end.

I guess this could be a possible vet check?

@adonovan @timothy-king

vet could warn about "ast"-identical, side effect free, non-pointer* struct keys in map composite literals. Seems feasible to do it.

It is not clear how often people would write map[struct{}]int though. This is an unclear way to write an optional int compared to struct{int; bool} or *int. For more complex examples does this happen in practice? So I am worried about meeting the frequency requirement for vet (README). Is there another example that happened in practice? Maybe this is just theoretically surprising?

[*] with maybe an exception for *struct{}.