Re: [go-nuts] Re: Why are two slices in this example less costly than one?

I told you the reason already. slice of struct is in the stack frame. Am Freitag, 13. Oktober 2017 16:59:14 UTC+2 schrieb Gabriel Aszalos: > > > For some reason, it seems that allocating a slice of slices takes up quite > a bit of memory, while allocating the slice of structs takes up no memory?

[go-nuts] Re: Correct checkout branch go1.9 in 'Installing Go from source'

It's a tag. git tag -l will list it. Am Dienstag, 29. August 2017 14:55:24 UTC+2 schrieb Will Zhou: > > In the page Installing Go from source > , of the section below, branch > 'go1.9' should be changed to 'release-branch.go1.9'. > > > Fetch the repository

[go-nuts] Re: FAIL: TestBuildmodePIE

This is https://github.com/golang/go/issues/21452 Am Freitag, 18. August 2017 13:31:16 UTC+2 schrieb SauliusGurklys: > > Hi, > > I'm using > > $ uname -a > Linux alio 4.11.12-1-MANJARO #1 SMP PREEMPT Fri Jul 21 08:51:46 UTC 2017 > x86_64 GNU/Linux > > For a couple of days my go build from

[go-nuts] Re: [security] Go 1.7.6 and Go 1.8.2 are released

https://groups.google.com/forum/#!forum/golang-announce Am Mittwoch, 24. Mai 2017 04:58:43 UTC+2 schrieb Henry: > > Is there some kind of a mailing list (for Go releases only), so that we > can be notified of new releases via email? > > -- You received this message because you are subscribed

[go-nuts] Re: thread safety of map when each goroutine access a different key

Why do you even use a shared map, if you only use distinct keys per goroutine. There probably is a better pattern for your use case. Am Montag, 13. März 2017 07:39:59 UTC+1 schrieb Albert Tedja: > > Hello, > > I know map itself isn't threadsafe, but I am just wondering how threadsafe > it is if

Re: [go-nuts] Re: constant 256 overflows byte

memoryBlock[2] += (256-187) Am Mittwoch, 8. März 2017 01:48:08 UTC+1 schrieb Eric Brown: > > Actually, I didn't catch the int() in your example. I tried it, and it > worked! Thank you... > > On Tuesday, March 7, 2017 at 6:47:11 PM UTC-6, Eric Brown wrote: >> >> Thanks for the reply, Ayan. I

[go-nuts] Re: Is it a compiler bug?

What should be wrong? It is as intuitive as it can be. Did you ever wrote a lexer/tokenizer? Am Sonntag, 13. November 2016 08:38:03 UTC+1 schrieb imd3c: > > OK, I get it. It's in the spec, I had to check it. But still, isn't it > wrong? What's the point, is it tradition or something? I checked

Re: [go-nuts] regexp with ^

Thanks, worked. Am Samstag, 15. Oktober 2016 22:16:14 UTC+2 schrieb Shawn Milochik: > > Escape the carat with the backslash. > > https://play.golang.org/p/SX_q0KuIvU > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this

[go-nuts] regexp with ^

Hello, I have the problem, that I want to match expressions like: bar_f00^42 , but "[[:alpha:]]+_[[:alnum:]]+^[[:digit:]]+" won't work because of the '^'. So what are my options? Best, Marvin -- You received this message because you are subscribed to the Google Groups "golang-nuts" group.

Re: [go-nuts] differences between pointer and value slice in for-range loop

https://play.golang.org/p/bVizbGIMDp should work -- 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,

Re: [go-nuts] differences between pointer and value slice in for-range loop

https://play.golang.org/p/9LQMDrDIOv should work. -- 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,

[go-nuts] Re: differences between pointer and value slice in for-range loop

Because print() is called on different pointer values. -- 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