Re: [go-nuts] why in source of go compiler, initialize a *gc.Node with the help of a temp struct x? can't we initialize it directly?

On Tue, Dec 25, 2018 at 10:13 PM wrote: > > I notice in the source comiler go initialize a Node n use a temp x, why the > variable n is initialized like this? > > why just initilize the n like below? > n = new(Node) > n.Func = new(Func) > > > > the source from File: src/cmd/compile/internal/gc/su

[go-nuts] why in source of go compiler, initialize a *gc.Node with the help of a temp struct x? can't we initialize it directly?

I notice in the source comiler go initialize a Node n use a temp x, why the variable n is initialized like this? why just initilize the n like below? n = new(Node) n.Func = new(Func) *the source from File: src/cmd/compile/internal/gc/subr.go* func nodl(pos src.XPos, op Op, nleft, nright *Node)

Re: [go-nuts] go modules go build fails - normal go build with $GOPATH set works

On Wed, Dec 26, 2018, 3:07 PM Sam Whited wrote: > This sounds like the version is mismatched. Is the gopath version a newer > commit (with api changes) than the tag being picked in the go.mod file? I > have this quite frequently with golang.org/x/text which was last released > some time ago and h

Re: [go-nuts] go modules go build fails - normal go build with $GOPATH set works

This sounds like the version is mismatched. Is the gopath version a newer commit (with api changes) than the tag being picked in the go.mod file? I have this quite frequently with golang.org/x/text which was last released some time ago and have to use a replace directive to get a more up to date

[go-nuts] go modules go build fails - normal go build with $GOPATH set works

I have been testing out the new go modules feature. Our application compiles/installs without problems using the normal $GOPATH way and have been using this for a while now. trying go modules produces the same error over and over Steps I followed unset $GOPATH just to be safe 1) git clon

[go-nuts] [gollvm] Can't retrieve LLVM intermediate representation

Hi! I'm currently trying to retrieve the LLVM IR from the compilation process. To do so, I followed the given instructions. From my perspective I'm not missing anything, but I can't get llvm-goc to emit the llvm IR. I created a transcript and added parameters to the the original call to llvm-go

Re: [go-nuts] Go “service container” thoughts

I've repeatedly built "service container" or "corp kits" like the one you're describing, as well as helped a number of orgs improve their own versions of the thing in a consultant capacity. I think everyone has the same reaction that you do: why are we duplicating all this effort? But I can say wit

[go-nuts] runtime.readmemstats -> buckhash_sys increase

Hi Not using cgo at all. -- 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. For more options, visit https://groups.google.

Re: [go-nuts] Re: Best practices for using methods on types to write SQL

You can try https://github.com/xwb1989/sqlparser which is a MySQL parser and writer which is extracted from YouTube's vitessio/vitess . We have it forked to support SQL-92 standard https://github.com/CovenantSQL/sqlparser Also, we have some examples in our simple

Re: [go-nuts] go get can not download git submodule

I end up testing git subtree, it works in my testing. Justin Israel 于2018年12月25日周二 下午1:43写道： > > > On Tue, Dec 25, 2018, 4:17 PM xiang liu wrote: > >> Thanks a lot! >> >> It seems go 1.11 does not support git submodule. go 1.10 works fine. >> > > Oh, I wonder if they ended up getting rid