Re: [go-nuts] About the efficency of modifying map elements.

Isn't this really just another form of issue 3117 ? On Wed, Mar 17, 2021 at 3:19 PM 'Axel Wagner' via golang-nuts < golang-nuts@googlegroups.com> wrote: > On Wed, Mar 17, 2021 at 10:06 PM tapi...@gmail.com > wrote: > >> For simple scenarios, compiler op

Re: [go-nuts] Go PostgreSQL? pg versus pgx

b 22, 2021 at 7:56 AM Paul Förster wrote: > Hi Matthew, > > > On 22. Feb, 2021, at 15:28, Matthew Holiday > wrote: > > > > From the "status" section at the bottom of the README for pq: > > > > "This package is effectively in maintenance mode

Re: [go-nuts] Go PostgreSQL? pg versus pgx

>From the "status" section at the bottom of the README for pq: "This package is effectively in maintenance mode and is not actively developed. Small patches and features are only rarely reviewed and merged. We recommend using pgx which is actively maintained." On Mon, Feb 22, 2021 at 7:19 AM Paul

Re: [go-nuts] Error handling

ou know by looking at the code, or even compiling the > code, that all possible errors returned by a function are handled? That to > me is biggest difficult in reading (or using) others Go code. Exceptions > (well written) handle this by declaring all possible error (or categories) >

Re: [go-nuts] Error handling

Roger beat me to it. But allow me to rephrase, "The users of Go for a long time have resisted any changes to its simple, clear method of error handling despite it being a major concern of folks who don't use Go much." * * I'm referring to the original survey, which was worded along the lines of

Re: [go-nuts] Re: Possible Go 2 proposal for built-in Remove method for Slices.

See also this graphical cheat sheet: https://ueokande.github.io/go-slice-tricks/ On Fri, Feb 5, 2021 at 2:09 AM Brian Candler wrote: > See: https://github.com/golang/go/wiki/SliceTricks#delete > (and lots of other neat tricks there). > > There's no need to add new syntax or functions when the ex

Re: [go-nuts] Code compiles with unused var block

You are correct sir, and unfortunately, go vet doesn't find it either. But if you lint your code with golangci-lint ( https://github.com/golangci/golangci-lint) the deadcode linter will find it for you. On Wed, Feb 3, 2021 at 9:35 AM Danny Hart wrote: > Hello all, > > Very new gopher here (also