Menu
I am fed up with the error
main.go:10:5: import cycle not allowed
The bug does not give information, where is the dependency cycle and does not even tell which file is the problem. Is there a way I can find out the dependency cycle or dependency diagram in go? As the codebase goes large its very difficult to deduce this.
703
Let's say we have two packages, p1 and p2 . When package p1 depends on package p2 and package p2 depends on package p1 , it creates a cycle of dependency.
So what is a cyclic dependency? Let's say we have a struct A and struct B in package 'a' and 'b' respectively. struct A is dependent on struct B and struct B is dependent on struct A, then we can say there is a cyclic dependency or an import cycle in Golang.
You cannot trick the Go compiler, and that is a good thing. This restriction has been made by design. It is supposed to ease the compilation process, and give the project a single direction.
To import a package, we use import syntax followed by the package name. 💡 Unlike other programming languages, a package name can also be a subpath like some-dir/greet and Go will automatically resolve the path to the greet package for us as you will see in the nested package topic ahead.
And the collective answer based on comments above:
Its a known issue, recently fixed so look out for a new release or compile the go tool from source.
(Contributed by: @MatrixFrog, @infantDev, @jnml and @nemo)
131
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
