>
> I don't like the idea of giving go run any more powers. It is already
>> being horribly abused.
>>
>
> I understand the sentiment; it needn't be the run sub-command of course...
> it's about adding this behaviour to the go command.
>
Because I'm lacking imagination, it could be an entirely sep
>
> > go run github.com/fruit/banana arg1 arg2 ...
>
> I don't like the idea of giving go run any more powers. It is already
> being horribly abused.
>
I understand the sentiment; it needn't be the run sub-command of course...
it's about adding this behaviour to the go command.
> Your users can
On Thu, Mar 30, 2017 at 11:28 AM Paul Jolly wrote:
> go run github.com/fruit/banana arg1 arg2 ...
I don't like the idea of giving go run any more powers. It is already being
horribly abused. Your users can perhaps try
$ $GOPATH/bin/banana arg1 arg2
if properly setting PATH is beyond wh
I've searched golang-nuts and the Go issue tracker pretty extensively and I
can't find any mention of my question or the topic, so would appreciate any
links if this has been previously covered and I was simply using the wrong
search terms.
go install takes a number of packages as arguments:
$
