There is an important distinction: - users of your project / library are interested in hard dependencies of it - developers / testers of your library will actually be using its test dependencies
Go modules enforces the first group your test dependencies as hard dependencies, which is not right. 26 Eki 2019 Cmt 02:49 tarihinde Cody Oss <the.cody....@gmail.com> şunu yazdı: > A dependency is a dependency. There are no scopes like you might find in > Maven(Java) land. Your project needs these "test deps" to run your tests, > so they are in your module file. Even so, Go is smart enough when it builds > your binary to not include the extra bloat. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "golang-nuts" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/golang-nuts/4kldLhXlfAU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/6269fe14-6708-48e9-ad98-62b2aadd3866%40googlegroups.com > . > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAPqC6xRLLSn%3Db9OLBmQwjJxujYZwXqEd5Z_KbNrn9Rmn1EFE-Q%40mail.gmail.com.
