News for hackers. Stuff that matters.
Re:Go and Versioning: Minimal Version Selection by lboasso on Wednesday February 21, 2018 @07:29PM (#16434223)
> Note that F 1.1 requires G 1.1, but G 1.1 also requires F 1.1. Declaring this kind of cycle can be important when singleton functionality moves from one module to another. Our algorithms must not assume the module requirement graph is acyclic.

I thought we cannot have cycles in Go packages. The Go spec says "The importing of packages, by construction, guarantees that there can be no cyclic initialization dependencies." What am I missing?

Re:Go and Versioning: Minimal Version Selection by xiaq on Wednesday February 21, 2018 @08:02PM (#16434360)
A module can contain multiple packages. You can have a dependency graph like F/a -> G/a -> F/b.
Re:Go and Versioning: Minimal Version Selection by lboasso on Wednesday February 21, 2018 @08:09PM (#16434392)
It makes sense now, Thanks!