On 2016-07-16 17:59, Mauro Toffanin wrote:
But wrt. to the talk above: Didn't Dave Cheney dismiss the diamond
problem a little too fast? Sure you "cannot" do that, but you can still
end up in a situation where you depend on 2 different libraries, each
which depends on different specific version of the same 3rd package.
I actually agree with Cheney's decision:
http://dave.cheney.net/2015/06/09/gb-a-project-based-build-tool-for-the-go-programming-language
The probability of encountering a diamond dependency conflict is so low
that makes sense to treat it like a corner case and to force the final
user to manually take action;
Yes... I would agree with that too.
... since there's in principle no way to know whether it's at all
possible to resolve that conflict without patching the libraries to
support the same version of the common dependency.
/Peter
--
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.
