Thanks for that, this will come in handy for editing the go.mod file.
But I'd like to avoid editing the file at all.
On Monday, August 5, 2019 at 7:16:08 PM UTC+2, Paul Jolly wrote:
>
> Take a look at go mod edit
>
> https://golang.org/cmd/go/#hdr-Module_maintenance
>
>
>
> On Mon, 5 Aug 2019, 18
On Mon, Aug 5, 2019 at 5:56 PM Shane H wrote:
>
> I've done a bit of searching, and asked around, but not found an answer to my
> (most likely self-inflicted) problem.
>
> I have been coding with Go 1.10 and 1.11 for a whiles, but I decided that it
> was time to join the future and upgraded to 1
On 6/8/19 11:38 AM, lgod...@gmail.com wrote:
> For f1 defined as func f1(k1, k2, k3 int) (x1, x2 int) {..}
> and f2 defined as func f2(x,y int) (xR int) {..}
>
> Why does the compiler complain about the call stmt
> f2 ( f1 (1,2,3) ) ??
>
It shouldn't. What little you posted is
On Tue, Aug 6, 2019 at 1:38 PM wrote:
> For f1 defined as func f1(k1, k2, k3 int) (x1, x2 int) {..}
> and f2 defined as func f2(x,y int) (xR int) {..}
>
> Why does the compiler complain about the call stmt
> f2 ( f1 (1,2,3) ) ??
>
I'm not sure what you're asking.
The compiler
For f1 defined as func f1(k1, k2, k3 int) (x1, x2 int) {..}
and f2 defined as func f2(x,y int) (xR int) {..}
Why does the compiler complain about the call stmt
f2 ( f1 (1,2,3) ) ??
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" g
Actually, one more thought. If we require to contain a dot, should we apply
this check to the module name appears on the first line of the go.mod file?
Currently I think the check is applied to the modules listed in "require"
list, that means, I can define a module "foo", but not able to refer t
On Tuesday, August 6, 2019 at 11:31:40 AM UTC+10, Shane H wrote:
>
>
>
> On Tuesday, August 6, 2019 at 10:56:42 AM UTC+10, Shane H wrote:
>>
>> Hi all,
>>
>> I've done a bit of searching, and asked around, but not found an answer
>> to my (most likely self-inflicted) problem.
>>
>> I have been c
On Tuesday, August 6, 2019 at 10:56:42 AM UTC+10, Shane H wrote:
>
> Hi all,
>
> I've done a bit of searching, and asked around, but not found an answer to
> my (most likely self-inflicted) problem.
>
> I have been coding with Go 1.10 and 1.11 for a whiles, but I decided that
> it was time to j
I see. Makes sense.
Thanks,
Shizheng
On Mon, Aug 5, 2019 at 7:04 PM Ian Lance Taylor wrote:
> On Mon, Aug 5, 2019 at 12:33 PM wrote:
> >
> > We are using bazel to manage dependency and would like to migrate to
> modules and use JFrog's module proxy. We have many private modules, starts
> with
Hi all,
I've done a bit of searching, and asked around, but not found an answer to
my (most likely self-inflicted) problem.
I have been coding with Go 1.10 and 1.11 for a whiles, but I decided that
it was time to join the future and upgraded to 1.12. It worked fine for the
project I was creati
On Mon, Aug 5, 2019 at 12:33 PM wrote:
>
> We are using bazel to manage dependency and would like to migrate to modules
> and use JFrog's module proxy. We have many private modules, starts with a
> name like "foo", and we specify the internal git repo in bazel. Based on the
> understanding of m
Hi,
We are using bazel to manage dependency and would like to migrate to
modules and use JFrog's module proxy. We have many private modules, starts
with a name like "foo", and we specify the internal git repo in bazel.
Based on the understanding of module proxy protocol, as long as the proxy
r
Take a look at go mod edit
https://golang.org/cmd/go/#hdr-Module_maintenance
On Mon, 5 Aug 2019, 18:45 Peter Feichtinger, wrote:
> Hi Go Nuts,
>
> I have a rather unusual use case and I'm hoping for some input.
>
> For testing purposes, I want to build a Go binary with different versions
> of
Hi Go Nuts,
I have a rather unusual use case and I'm hoping for some input.
For testing purposes, I want to build a Go binary with different versions
of one of its dependencies. The only way I could think of was to modify the
go.mod file to add a replace directive with the version I want to tes
On Monday, August 5, 2019 at 9:33:08 AM UTC-6, burak serdar wrote:
>
> On Mon, Aug 5, 2019 at 9:20 AM B Carr >
> wrote:
> >
> > Oh. I'm talking about env variables which a goroutine sets by using
> os.Setenv() which to me implies OS env variables. Are those env variables
> accessible by all
On Mon, Aug 5, 2019 at 9:20 AM B Carr wrote:
>
>
>
> On Monday, August 5, 2019 at 8:52:41 AM UTC-6, burak serdar wrote:
>>
>> On Mon, Aug 5, 2019 at 8:47 AM B Carr wrote:
>> >
>> > Is it safe to say that environment variables (accessible to all
>> > goroutines) also live in the data segment?
>>
On Monday, August 5, 2019 at 8:52:41 AM UTC-6, burak serdar wrote:
>
> On Mon, Aug 5, 2019 at 8:47 AM B Carr >
> wrote:
> >
> > Is it safe to say that environment variables (accessible to all
> goroutines) also live in the data segment?
>
> No.
>
> When you say "environment variables", do y
On Mon, Aug 5, 2019 at 8:47 AM B Carr wrote:
>
> Is it safe to say that environment variables (accessible to all goroutines)
> also live in the data segment?
No.
When you say "environment variables", do you mean OS env variables, or
the variables visible to a goroutine?
If you're talking about
Is it safe to say that environment variables (accessible to all goroutines)
also live in the data segment?
--
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
For those who haven't already noticed, I thought I'd point out that the
draft design has now been changed (as Ian intimated it might be) so that
contracts may now require a pointer method in some cases i.e. if the type
parameter is T one can now specify that *T has a certain method.
In particul
Hi Clement,
it's a nice investigation of the benefits and limits of using reflect.
I guess it would also be as interesting to investigate what this library
would look like if the current draft for generics were to be accepted :)
-s
On Sun, Aug 4, 2019 at 4:13 PM clement auger
wrote:
> You te
21 matches
Mail list logo
