cmd/compile: incorrect initialization order #9094
Labels
Milestone
Comments
|
Is this different from #7692? |
|
I don't really see how they are related. This issue is about the initialization order of global variables, which, given two variables with the same number of dependencies, should initialize them in source declaration order. |
|
@rsc @paranoiacblack They are not related. This is an actual bug. #7692 is about a feature request (Assignable is not implemented for go/types' Tuple types). |
rsc
changed the title
|
This appears to be a duplicate of #7962. |
|
@paranoiacblack agreed. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
$ cat incorrect_init.go package main var ( a = p("a") + c + b b = p("b") + f() c = p("c") + f() d = p("d") + 3 ) func f() int { d++ return d } func p(s string) int { println(s) return 0 } func main() { println(a, b, c, d) } compiling and executing produces: $ go run incorrect_init.go d c b a 9 5 4 5 But the correct order per the spec should be: d, b, c, a, with values 9, 4, 5, 5. See: http://tip.golang.org/ref/spec#Package_initializationThe text was updated successfully, but these errors were encountered: