[go-nuts] Re: Go 1.16.7 and 1.15.15

Ok lazyreader (IRC) has discovered that the release has a commit, relating to a CVE on handler panics that we think is the reason for the release (fixed my previously erroneous assertion of a single commit, and tidied up the wording a little) The changeset is https://go-review.googlesource.co

[go-nuts] Re: Go 1.16.7 and 1.15.15

Ok lazyreader (IRC) has discovered that the release has a single commit, relating to a CVE relating to handler panics The changeset is https://go-review.googlesource.com/c/go/+/338551/2/src/net/http/httputil/reverseproxy.go On Thursday, August 5, 2021 at 8:30:23 AM UTC+10 shan...@gmail.com wrote

[go-nuts] Go 1.16.7 and 1.15.15

Hi all My bot picked up that there was a release from github of Go for versions 1.16.7, and 1.15.15 But I cannot find any release notes or supporting documentation, and the release hasn't (yet) made it to downloads Was this an unintentional release? -- You received this message because you

[go-nuts] [HIRING] Sr. Software Engineers - Developing & Scaling Applications in Go.

*The Role:* We’re looking for talented and motivated engineers with 4+ years of experience as a professional software engineer. Our engineers own entire features in our system. You'll influence the initial specs for the feature, build/modify the backend , write the front-end code to polish

[go-nuts] Go Doc Tip and Request

I've been dabbling in Go since 2009 -- I grew accustomed to godoc.com, and the way godoc formats the documentation. Not that the new pkg.go.dev isn't any good -- its a matter of preference because you're used to seeing it one way, and pkg.go.dev displays it another. I am not a full time develope

Re: [go-nuts] Behavior to copy the value of pointer inside another pointer

Oh Yes, Thanks! Le mercredi 4 août 2021 à 17:25:39 UTC+2, bse...@computer.org a écrit : > On Wed, Aug 4, 2021 at 9:18 AM Olivier Szika wrote: > >> Hi all, >> >> I am surprised by the behavior of "&(*var)". >> > > According to the language spec, pointer indirection is addressable: > > https://go

Re: [go-nuts] Behavior to copy the value of pointer inside another pointer

Yes. From the spec : For an operand x of pointer type *T, the pointer indirection *x denotes *the > variable* of type T pointed to by x. Emphasis mine. "The variable", means it really denotes the storage location that `x` points to. Not the value or

Re: [go-nuts] Behavior to copy the value of pointer inside another pointer

On Wed, Aug 4, 2021 at 9:18 AM Olivier Szika wrote: > Hi all, > > I am surprised by the behavior of "&(*var)". > According to the language spec, pointer indirection is addressable: https://golang.org/ref/spec#Address_operators Thus, taking the address of an indirection yields the original poin

[go-nuts] Behavior to copy the value of pointer inside another pointer

Hi all, I am surprised by the behavior of "&(*var)". https://play.golang.org/p/CK522lRkddd It is expected? -- 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 gola

[go-nuts] Re: go list -u -m -json all

Go 1.17RC2 fixes this issue. Thanks all contributors. Le lundi 26 juillet 2021 à 09:11:53 UTC+2, Jérôme LAFORGE a écrit : > FYI, I just seen an issue has been already opened : > https://github.com/golang/go/issues/47377 > > Le dimanche 25 juillet 2021 à 21:02:29 UTC+2, Jérôme LAFORGE a écrit : >

Re: [go-nuts] How to use errors.As with sentinel errors?

Opened https://github.com/golang/go/issues/47528 On Monday, August 2, 2021 at 6:30:04 PM UTC+2 Andreas Götz wrote: > > Because both are of type `*errors.errorString`, so the types match and > it copies over the value. > Arguably, `errors.errorString` should implement `As()` and return `false`,