Re: [go-nuts] go env GOPATH not reflecting $GOPATH

2017-09-02 Thread Val
Hello burp, I'm glad you could solve your issue using 'export' in init scripts. Note that if you choose ~/go (instead of ~/Dev/go) then you don't even need a GOPATH environment variable, it is regarded as the default gopath by most of the go ecosystem >=1.8. This is intended to save these modera

Re: [go-nuts] go env GOPATH not reflecting $GOPATH

2017-09-02 Thread Val
I meant "instead of /home/dev/devSync/workspace". (Perks of replying with phone, couldn't see OP while typing.) -- 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 g

Re: [go-nuts] Struct overloading method issue

2017-09-02 Thread Jesse McNelis
On Sat, Sep 2, 2017 at 12:50 AM, BeaT Adrian wrote: > Hello, I ran into a strange scenario and I wanted to know if there is a > better solution for it > > type A struct{} > > func (a *A) private() {} > func (a *A) Public() { >a.private() > } > > type B struct {A} > > func (b *B) private() {} >