Re: [go-nuts] Re: go 1.13 won't compile

2019-09-28 Thread Robert Solomon
I'm getting the sense that my question is below getting an answer I can understand and follow. Is there a more suitable site for me to post my question without irritating people? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscri

Re: [go-nuts] Re: go 1.13 won't compile

2019-09-27 Thread Ian Lance Taylor
On Thu, Sep 26, 2019 at 11:08 AM Robert Solomon wrote: > > Should I file an issue I recommend that you use package paths whose first element is a domain name. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group a

[go-nuts] Re: go 1.13 won't compile

2019-09-26 Thread Robert Solomon
Should I file an issue -- 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:

[go-nuts] Re: go 1.13 won't compile

2019-09-24 Thread Robert Solomon
Sometimes I hate autocorrect I mean ~/go/src -- 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

[go-nuts] Re: go 1.13 won't compile

2019-09-23 Thread Robert Solomon
If I understand you, you want me to not use ~/go/sec? That confuses me. Am I getting expected behavior? -- 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 golan

[go-nuts] Re: go 1.13 won't compile

2019-09-23 Thread Dmitry Savintsev
> I do not have, need or use a go.mod. I would still recommend to give it a try - it will likely make your Go dev life easier :) Try to follow this recipe - you probably don't need to understand much of what's going on "up front" to get your code to build/test: * assuming your Github / Gitlab