[go-nuts] why we still need lock file ?

As go is using minimum version selection strategy for creating reproducible build list, so why we still need a lock file ? also is there plans to deprecate lock file in future ? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe fr

Re: [go-nuts] How does bytealg.MakeNoZero() work?

And in terms of practical advice: You might be able to use go:linkname yourself to get access to that functionality from the runtime. But note that go:linkname is being locked down in Go 1.23 , so that is not a future-proof plan. Your best bet is probabl

Re: [go-nuts] How does bytealg.MakeNoZero() work?

It is defined in the runtime and go:linkname'd into the bytealg package: https://github.com/golang/go/blob/90bcc552c0347948166817a602f612f219bc980c/src/runtime/slice.go#L394 >From the spec : > A function declaration without type parameters may omit t

[go-nuts] How does bytealg.MakeNoZero() work?

Can someone help me understand how `bytealg.MakeNoZero()` in the Go standard library works, please? https://github.com/golang/go/blob/master/src/internal/bytealg/bytealg.go#L118 In the source it is a `func` without

Re: [go-nuts] Comparison of pointers to distinct zero-sized variables

Hi, you might be interested to learn that Ian has filed a CL adding an FAQ entry . On Thu, 20 Jun 2024 at 16:18, Oliver Eikemeier wrote: > Thanks for that example. > > The issue is that you and I have constructed aliased variables that the

[go-nuts] Re: Performance of unique package

The unique package itself has a few benchmarks you can run if you'd like, though they're somewhat limited. They exist primarily to validate that the implementation has

[go-nuts] Performance of unique package

Hi, Does anyone have any benchmarks for the new "unique" package? How does it compare with manual interning using a map? Thanks. -- 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,

Re: [go-nuts] Re: encoding/json treats []byte as b64 encoded. Could it not?

Related: https://stackoverflow.com/a/78662958/3768429 On Monday 16 December 2013 at 19:37:30 UTC+1 Kyle Lemons wrote: > On Sun, Dec 15, 2013 at 2:05 PM, Brian Picciano > wrote: > >> I'm going to compress my three responses to one. >> >> > What I'm less clear on is exactly what your use case is