Comment 1:

Labels changed: added repo-main, release-go1.4.

Comment 2:

CL https://golang.org/cl/102030043 mentions this issue.

Comment 3:

Can you please try this CL https://golang.org/cl/102030043?

Comment 4:

CL https://golang.org/cl/145820044 mentions this issue.

Comment 5:

Your CL makes reference to V8 and Python. That's not interesting. This is Go. The Go
rule is that if you have two embedded structs with the same field name at the same depth
in a struct type, that field name is not accessible from the top level of the struct
using the . operator.
json.Marshal uses all the fields that are accessible from the top level using the .
operator. If there are JSON-specific tag overrides, it applies the same Go rule to those
instead of the Go field names. But either way it is the Go semantics that are being used
here, not anything defined by JSON or V8 or Python.
To be very concrete, here is an edited version of your program:
http://play.golang.org/p/aFmsL3WA-L
package main
import (
    "fmt"
)
func main() {
    type a struct {
        Hello string
    }
    type b struct {
        Hello string
    }
    type c struct {
        a
        b
    }
    
    herp := c{a{"hello"},b{"world"}}
    fmt.Println(herp.Hello)
}
This doesn't compile. There is no herp.Hello. Therefore json.Marshal does not marshal
one.

Status changed to WorkingAsIntended.

Comment 6 by trey@jellolabs.com:

Don't you think that json.Marshal should return a runtime error similar to the one given
by the compiler in your example?