Re: [go-nuts] Order of evaluation need more definition in spec

ession, shows a warning say the execution order is unspecified may cause bug? On Thursday, March 14, 2019 at 8:04:12 PM UTC-7, Ian Lance Taylor wrote: > On Thu, Mar 14, 2019 at 2:49 PM zshi via golang-nuts > > wrote: > > > > I'm a little bit confused with result from

[go-nuts] Order of evaluation need more definition in spec

I'm a little bit confused with result from below code: func change(v *int) bool { *v = 3 return true } func value(v int) int { return v } func main() { b := 1 fmt.Println(b + 1, value(b + 1), change(&b)) } Output: 4 2 true I expected 2 2 true. Then I checked spec