alt Hacker NewsI don’t see how it breaks anything if it’s opt-in. By default you get the current behavior with zero value initialization if that’s what you want (and in many cases it is). But if you’d rather force an explicit value to be supplied, what’s the harm?
I don’t see how it breaks anything if it’s opt-in. By default you get the current behavior with zero value initialization if that’s what you want (and in many cases it is). But if you’d rather force an explicit value to be supplied, what’s the harm?
> I don’t see how it breaks anything if it’s opt-in?
Zero values are a fundamental, non-optional, "feature" of Go.
> But if you’d rather force an explicit value to be supplied, what’s the harm?
What happens if you use the function above with your type?
Or reflect.Zero?