On Fri, 2021-09-24 at 11:21 +0100, Ian Davis wrote: > This is not a correct interpretation. In your example the > unmarshaller reads the incoming json. The first key encountered is > "Name" and it matches exactly with the field named and tagged as Name > so that field is assigned the value. The next json key encountered is > "name" which does not match any field exactly so the unmarshaller > falls back to a case insensitive match and assigns the value to the > Name field, overwriting the previous value.
Yeah, you're right. I was not thinking about the mechanism correctly. My point stands wrt the impact on utility though. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/22f4f41630b22949d8161a0d63e2ebd239d6f714.camel%40kortschak.io.
