Is the "static initialization order fiasco" a thing that can happen in go? The order of package level variable initialization is well defined in the spec and be

Is the "static initialization order fiasco" a thing that can happen in go? The order of package level variable initialization is well defined in the spec and because go doesn't allow import cycles it seems like the issue mentioned in the linked page is not possible.