[go-nuts] Re: [ANN] peanut - write tagged structs to disk, in a variety of formats

Oh — it also has a few writers that can be helpful during development and testing: swap the file writers for a log writer (or discard writer) during development (handy if your program usually spits out a lot of output files), and swap in the mock writer for easy testing. /J On Tuesday, April 20

[go-nuts] [ANN] peanut - write tagged structs to disk, in a variety of formats

Hi there fellow Go Nuts and Gophers, Whilst working on a project not long back, I created a library to easily write tagged structs to disk, in a variety of output formats. https://github.com/jimsmart/peanut Each writer has a simple Write method, that takes a tagged struct. Each type of struct

Re: [go-nuts] Trying to port Go to HPE NonStop x86 - Need some guidance

On Tue, Apr 20, 2021 at 1:39 AM Shiva wrote: > > I'm a bit confused now. Let me explain what I have been doing. > 1. Installed go on windows (go version go1.4-bootstrap-20170531 windows/amd64) > 2. Duped linux files to nsx and added build statements > At this point, I am not supposed to run bootst

Re: [go-nuts] TotalAlloc dropped in runtime/metrics

Oh, actually, you can compute Mallocs and Frees from allocs-by-size and frees-by-size (summing the total # of samples). You can only estimate TotalAlloc though, which is genuinely missing. On Tue, Apr 20, 2021 at 3:14 PM Michael Knyszek wrote: > Oh gosh, I think TotalAlloc, Mallocs, and Frees ar

[go-nuts] Re: go build ./... will produce a binary of one and only one main package is found

Il giorno martedì 20 aprile 2021 alle 21:26:33 UTC+2 Manlio Perillo ha scritto: > Il giorno martedì 20 aprile 2021 alle 09:08:02 UTC+2 Brian Candler ha > scritto: > >> I agree with the OP: it would be less surprising if "go build ./..." >> always did build and store the artefacts, and there wer

[go-nuts] Re: go build ./... will produce a binary of one and only one main package is found

Il giorno martedì 20 aprile 2021 alle 09:08:02 UTC+2 Brian Candler ha scritto: > I agree with the OP: it would be less surprising if "go build ./..." > always did build and store the artefacts, and there were a separate flag to > discard them. > > Currently, "go build ./..." discards the build

Re: [go-nuts] TotalAlloc dropped in runtime/metrics

Oh gosh, I think TotalAlloc, Mallocs, and Frees are actually an oversight on my part. Sorry about that. They're very easy to add and I can probably even add them for this release. Please do use the new runtime/metrics package! Most of the other metrics should be there in some form (e.g. the divis

Re: [go-nuts] TotalAlloc dropped in runtime/metrics

[ + mknyszek ] On Tue, Apr 20, 2021 at 11:12 AM Marco A. wrote: > > Hi everyone, > > I was considering using the new stable metrics interface with go 1.16 > (https://golang.org/pkg/runtime/metrics/) for our program and I was also > wondering why things like TotalAlloc > (https://golang.org/pkg

Re: [go-nuts] Re: help with the Google Pub/Sub Go client API

Ack. Yeah, I totally agree with some of your points. I'll create a tracking issue to improve the comments and the docs. Thanks a ton for the feedback! On Monday, April 19, 2021 at 4:10:14 PM UTC-7 kortschak wrote: > Comments in-line. > > On Mon, 2021-04-19 at 15:08 -0700, 'hong...@google.com' vi

[go-nuts] TotalAlloc dropped in runtime/metrics

Hi everyone, I was considering using the new stable metrics interface with go 1.16 (https://golang.org/pkg/runtime/metrics/) for our program and I was also wondering why things like TotalAlloc (https://golang.org/pkg/runtime/#MemStats) had been dropped in the available metrics. Any particular

[go-nuts] [ANN] go-portable and go-compatible

Recently I have started to send some CL to the Go project, and I wanted some tools to check the portability to other platforms and the compatibility to older Go releases of my changes. https://github.com/perillo/go-portable checks if a package is portable to all the platforms supported by go.

Re: [go-nuts] Trying to port Go to HPE NonStop x86 - Need some guidance

Ian, I'm a bit confused now. Let me explain what I have been doing. 1. Installed go on windows (go version go1.4-bootstrap-20170531 windows/amd64) 2. Duped linux files to nsx and added build statements At this point, I am not supposed to run bootstrap.bash but run make.bat because my installati

[go-nuts] Re: go build ./... will produce a binary of one and only one main package is found

I agree with the OP: it would be less surprising if "go build ./..." always did build and store the artefacts, and there were a separate flag to discard them. Currently, "go build ./..." discards the build artefacts under certain conditions, see this example