On Tue, Feb 19, 2019 at 10:04 AM Harald Weidner <hweidner-li...@gmx.net> wrote: > > I would also consider the order in which init() functions of the same > package are executed undefined. The spec says they are executed "in the > order they appear in the source, possibly in multiple files, as presented > to the compiler". However, I believe a command like "go run *.go" can > yield different orders, according to the shell, shell settings, or > filesystem charset/collation settings.
I agree about the specific case of `go run *.go`, but I want to clarify that when `go run` or `go build` are used to build a package rather than a list of files, they do pass the files to the compiler in a consistent way. Ian -- 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. For more options, visit https://groups.google.com/d/optout.
