Re: [go-nuts] How to interpret the HeapReleased decrease?

On Sat, Jun 18, 2022 at 6:35 AM Vitaly Isaev wrote: > > Hi everyone, I've read the thread https://github.com/golang/go/issues/33376, > but still I can't figure out what does it mean when HeapReleased value is > decreasing. > When the Go runtime returns the memory to the OS, isn't it an irreversib

[go-nuts] Show your support for GitHub adding Gerrit features

https://github.com/github-community/community/discussions/18879 It would be nice if the Go project could do reviews on GitHub too. -- 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,

[go-nuts] How to interpret the HeapReleased decrease?

Hi everyone, I've read the thread https://github.com/golang/go/issues/33376, but still I can't figure out what does it mean when HeapReleased value is decreasing. When the Go runtime returns the memory to the OS, isn't it an irreversible process? So why does this indicator have to go down? Or

Re: [go-nuts] sync.Once: why atomic load is not needed after acquiring mutex lock?

Hi Axel, thanks. yeah, that sounds right. I was probably over thinking about all the cache coherency and consistency stuff. On Saturday, June 18, 2022 at 10:34:28 AM UTC+2 axel.wa...@googlemail.com wrote: > o.done is only written while o.m is locked. So there can't be any > concurrent writes t

Re: [go-nuts] sync.Once: why atomic load is not needed after acquiring mutex lock?

o.done is only written while o.m is locked. So there can't be any concurrent writes to that particular read. The store has to use atomic, as there *are* concurrent reads not protected by the mutex. On Sat, Jun 18, 2022 at 10:26 AM Xiaofan Hu wrote: > Hi, I have a question about sync.Once. > > In

[go-nuts] sync.Once: why atomic load is not needed after acquiring mutex lock?

Hi, I have a question about sync.Once. In *Once.doSlow , it isn't using atomic.LoadUint32 after acquiring the lock, isn't there a risk of race condition/data race here? ``` func (o *Once) doSlow(f func()) { o.m.

Re: [go-nuts] Go Fonts v2.010

On Fri, 17 Jun 2022 15:37:52 +1000 Nigel Tao wrote: > The Go Fonts were originally released > in 2016 and version 2.008 > > came out in 2017. It's taken longer that we'd have liked, but we have >