Did json.Unmarshal change behaviour between 1.13 and 1.15?

[alexec]

What version of Go are you using (go version)?

v1.13 and v1.15

Does this issue reproduce with the latest release?

Yes.

What operating system and processor architecture are you using (go env)?

Linux AMB 64.

What did you do?

I unmarshal into an existing object, and the values of a slice within that object get all jumbled up.

json.Unmarshal(data, &pod.Spec)

pod.Spec already exists and contains data.

What did you expect to see?

I'm actually not sure. If feels like the behavior changed, but unmarshalling into an object which already contains data - well I feel like I should expect problems.

What did you see instead?

[magical]

There was a CL targeted for 1.15 that changed the behavior of json.Unmarshal into existing slices, but it was reverted before the final release. See #21092 and #39427 for details. If you are running a beta of 1.15 that could be the cause.

[seankhliao]

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.

For questions please refer to https://github.com/golang/go/wiki/Questions