Re: [go-nuts] Breaking change: reflect.StructOf: field 0 has no name

On Mon, Dec 11, 2017 at 11:23 AM, wrote: > Is there any reason why this breaking change is not mentioned in any of the > release notes? The original code did not document how to create embedded fields, and the support that it did have did not work correctly (it did not set the

Re: [go-nuts] Breaking change: reflect.StructOf: field 0 has no name

Is there any reason why this breaking change is not mentioned in any of the release notes? On Monday, December 11, 2017 at 8:22:28 AM UTC+2, Ian Lance Taylor wrote: > > On Sun, Dec 10, 2017 at 8:46 AM, wrote: > > > > I had some code that I didn't touch for a while and now it

Re: [go-nuts] Breaking change: reflect.StructOf: field 0 has no name

On Sun, Dec 10, 2017 at 8:46 AM, wrote: > > I had some code that I didn't touch for a while and now it seems it's > broken. It panics with `reflect.StructOf: field 0 has no name` at runtime. > Wasn't Go supposed to have some sort of compatibility promise? > > After a while I've

[go-nuts] Breaking change: reflect.StructOf: field 0 has no name

I had some code that I didn't touch for a while and now it seems it's broken. It panics with `reflect.StructOf: field 0 has no name` at runtime. Wasn't Go supposed to have some sort of compatibility promise? After a while I've found this[1] issue which seems to be the reason why my program