Re: [go-nuts] Re: Golang API to fetch available versions and release features

You can check out the source code for https://go.dev/dl/ at https://github.com/golang/website/blob/master/internal/dl/dl.go On Mon, Jun 13, 2022 at 11:31 PM durgasomes...@gmail.com < durgasomeswararao...@gmail.com> wrote: > Hi Amnon, > > Thanks for the information you shared. > Where can I

Re: [go-nuts] Missing /usr/lib/go/pkg/include/ for native binaries

Looks like golang-1.18-go owns /usr/lib/go-1.18/pkg/include <<'SH_COMMANDS' docker run --rm -i debian:bookworm sh apt update && apt -y install apt-file && apt-file update && apt-file search /usr/lib/go-1.18/pkg/include SH_COMMANDS On Saturday, April 9, 2022 at 1:33:04 AM UTC-6 Brian Candler

Re: [go-nuts] What are debian:buster-slim advantages vs alpine ones?

ach can run on other linux/amd64 platforms, even though CGO was not disabled. As a side note, the resultant image for the above Dockerfile is 369MB, whereas golang:alpine is only 299MB. The size difference is /usr/local/go/pkg/linux_amd64_race, which golang:alpine does not include (but golang:buste

[go-nuts] Re: [generics] Generic functions calls little confusing to readers

Interesting find, I would expect type parameter declarations to be limited to interfaces. On Tuesday, June 16, 2020 at 2:54:02 PM UTC-7, Alexander Morozov wrote: > > For example consider this example https://play.golang.org/p/rfccpBoFIJN > There is no generics involved, but for person reading

[go-nuts] Re: The "leave "if err != nil" alone?" anti-proposal

If good Go code handles or wraps every error, that code would never use 'try'. It seems weird to add a language feature that many codebases would discourage the use of. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this

[go-nuts] Re: telling apart errors returned by database/sql

The `pq.PGError` class appears to be deprecated and it's now suggested to use `pq.Error`. Here's a more concrete example of an insert failing due to a constraint violation (on conflict clause...) if err, ok := err.(*pq.Error); ok &&