how is a nil map not null? It certainly isn’t a zero-valued map, that would be {...

atombender · 2025-09-09T23:14:58 1757459698

The zero value of a map is indeed nil in Go: This prints true (https://go.dev/play/p/8dXgo8y2KTh):

    var m map[string]int
    println(m == nil)

binary132 · 2025-09-10T00:50:27 1757465427

Ok, true!

materielle · 2025-09-10T08:02:41 1757491361

It should be marshaled into {} by default, with a opt-out for special use cases.

There’s a simple reason: most JavaScript parsers reject null. At least in the slice case.

tubthumper8 · 2025-09-11T00:56:23 1757552183

Not sure what you mean here by "most JavaScript parser rejects null" - did you mean "JSON parsers"? And why would they reject null, which is a valid JSON value?

It's more that when building an API that adheres to a specification, whether formal or informal, if the field is supposed to be a JSON array then it should be a JSON array. Not _sometimes_ a JSON array and _sometimes_ null, but always an array. That way clients consuming the JSON output can write code consuming that array without needing to be overly defensive