[go-nuts] Re: gdb go optimized out

First of all, thank you very much for your answer. I use the giant font because I copied it directly from Google Translate. When I debug grow func of mheap.go file, I print the ask variable, it output No symbol "ask" in current context, print npage it output optimized out. func (h *mheap) grow(

Re: [go-nuts] Order of evaluation need more definition in spec

On Thu, Mar 14, 2019 at 2:49 PM zshi via golang-nuts wrote: > > I'm a little bit confused with result from below code: > > func change(v *int) bool { > *v = 3 > return true > } > > func value(v int) int { > return v > } > > func main() { > b := 1 > fmt.Println(b + 1, value(b +

[go-nuts] Re: Go 1.12.1 and Go 1.11.6 are released

Thanks for the note! Was hoping `math/pi` package to have been added on this date! :) On Thu, Mar 14, 2019 at 2:16 PM Katie Hockman wrote: > Hello gophers, > > We have just released Go versions 1.12.1 and 1.11.6, minor point releases. > > These releases include fixes to cgo, the compiler, the go

[go-nuts] Order of evaluation need more definition in spec

I'm a little bit confused with result from below code: func change(v *int) bool { *v = 3 return true } func value(v int) int { return v } func main() { b := 1 fmt.Println(b + 1, value(b + 1), change(&b)) } Output: 4 2 true I expected 2 2 true. Then I checked spec

[go-nuts] Go 1.12.1 and Go 1.11.6 are released

Hello gophers, We have just released Go versions 1.12.1 and 1.11.6, minor point releases. These releases include fixes to cgo, the compiler, the go command, and the fmt, net/smtp, os, path/filepath, sync, and template packages. View the release notes for more information: https://golang.org

[go-nuts] Re: gdb go optimized out

First off. Please don't use a giant font in this group. It adds no valuable information, and makes it seem like you are yelling at the reader. I use delve not gdb, so I can not speak directly to that. I use -gcflags="-N -l", and so far it has always produced

Re: [go-nuts] Re: Packaging a Go module for Nix

Hi Wael, I am curious if the approach outlined in this branch of the thread has continued to work for you so far, vs. perhaps you hit a snag after the initial success you reported below? Regards, thepudds On Wednesday, March 13, 2019 at 2:46:59 PM UTC-4, Wael Nasreddine wrote: > > On Monday, M

Re: [go-nuts] Re: Persistence of value, or Safely close what you expected

On Wed, 13 Mar 2019 at 23:01, Andrey Tcherepanov < xnow4fippy...@sneakemail.com> wrote: > There were couple of things I was implementing for our little in-house > server app. > One was (in)famous fan-out pattern for broadcasting messages to clients, > and one for job queue(s) that could run fast (

Re: [go-nuts] Re: Packaging a Go module for Nix

On Thursday, March 14, 2019 at 6:52:52 AM UTC+1, Wael Nasreddine wrote: > > I'm going to describe how I ended up packaging the go modules (and so far > it seems to work correctly). I have also replied inline below > > I'm using a two-phase approach to package Go modules for Nix: > >1. During t