Is it possible to get rid of the "go_default_library" name? about rules_go HOT 3 CLOSED

First of all, sometimes there are several Go packages in a directory, which have different set of build tags. Although it is not related to the question very well.

Second, go_default_library makes the mapping between Bazel package and Go package path simple. We can always assume that //path/to/lib:something is under the go package $go_prefix/path/to/lib/....

Technically it was not impossible to choose the design of //path/to/lib:lib but it adds another special case into the mapping and makes the implementation more complex. So I have no plan to change the design.

from rules_go.

I think once we have a working 'gazelle' BUILD file generator, this issue
will be less important

On Tue, Aug 16, 2016 at 9:46 AM, Yuki Yugui Sonoda <[email protected]

wrote:

First of all, sometimes there are several Go packages in a directory,
which have different set of build tags. Although it is not related to the
question very well.

Second, go_default_library makes the mapping between Bazel package and Go
package path simple. We can always assume that //path/to/lib:something is
under the go package $go_prefix/path/to/lib/....

Technically it was not impossible to choose the design of
//path/to/lib:lib but it adds another special case into the mapping and
makes the implementation more complex. So I have no plan to change the
design.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#66 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALF-0rTxrxWTJcBmQeo3pA8zYtcPpmM6ks5qgb83gaJpZM4Jk6Rw
.

from rules_go.

Agreed, I think this is fine to leave for now. Thanks.

from rules_go.