> Given the above, is it guaranteed that A's stores to X, Y and Z are
synchronized-before B's loads from X, Y and Z?
Yes. The writes of X, Y, and Z are sequenced before the atomic write to M,
the atomic write to M is synchronized before the atomic read of M (assuming
the read returns the result
On Sun, Oct 30, 2022, 6:38 PM eric...@arm.com wrote:
> > That appears to be the primary limit. That including a composite literal
> initializer that exceeds that limit, causing a more ambiguous error, >
> seems like a related, but secondary, issue.
>
> Yes, this seems to be a related question, se
I'm curious how often you perform such refactoring? In my experience such
changes are extremely rare and usually require other changes due to
differences in the API of the two third-party packages . Which means, in my
experience, expending effort to automate such import rewrites typically
requires
He doesn't get the job done.
在2022年10月22日星期六 UTC+8 06:20:53 写道：
> try https://pkg.go.dev/golang.org/x/tools/cmd/gomvpkg
>
>
> On Friday, 21 October 2022 at 16:58:57 UTC+1 mr@gmail.com wrote:
>
>> I'm looking for a tool like this, I've searched google and github and
>> can't find one, have yo
> That appears to be the primary limit. That including a composite literal
initializer that exceeds that limit, causing a more ambiguous error, >
seems like a related, but secondary, issue.
Yes, this seems to be a related question, see
https://github.com/golang/go/issues/9862. If we do not allo
Would it be possible to get narrower time windows for these security
releases?
A date without a specified time zone is a span of 48 hours which is
impossible for me to plan for. I can't stay up all night or reasonably ask
them from others just in case a Go security fix happens to drop at any time
On Sun, Oct 30, 2022 at 10:16 AM Konstantin Khomoutov wrote:
>
> | initially, y==0.
> |
> | goroutine 1:
> | x = 42
> | x = 99
> | atomic.Store(&y, 1)
> | x = 100
> |
> | goroutine 2:
> | if atomic.Load(&y) == 1 {
> |println(x)
> | }
>
> then would println have been guaranteed to still print 9
On Sun, Oct 30, 2022 at 08:47:41AM -0700, jake...@gmail.com wrote:
> I would like to give you a definitive answer, but the same question comes
> up in https://groups.google.com/g/golang-nuts/c/Gze1TRtdLdc/ and there is
> much disagreement and no clear resolution. (The initial question is not
>
This was to add query parameters but can anyone help me on how to add path
parameters
like
"http://mywebsite.com/:sub-path";
where sub-path is the path parameter having a string value like "about"
so the link becomes
"http://mywebsite.com/about";
On Friday, December 14, 2018 at 11:30:42 PM UTC+5
On Fri, Sep 16, 2022 at 01:26:05PM -0700, 'Keith Randall' via golang-nuts wrote:
> Atomic operations can establish happens-before relationships.
>
> initially, y==0.
>
> goroutine 1:
> x = 99
> atomic.Store(&y, 1)
>
> goroutine 2:
> if atomic.Load(&y) == 1 {
>println(x)
> }
>
> This progra
Based on my reading of the Go memory model, this algorithm sketch is
memory-race free. However, there is a race condition. Here's the reason:
The writer issues a synchronized-write to array pointer, and another
synchronized-write to the array len. A reader issues a synchronized read.
the correspo
Hi Konstantin
Thanks for the reply - this is exactly what I needed! It even seems
like tls.Conn has a function NetConn that allows me to get my net.Conn
back again. So for anyone stumbling on this in the future, I think
this is the way to solve it:
* Make the customer TLS dialer dial a TCP connec
I would like to give you a definitive answer, but the same question comes
up in https://groups.google.com/g/golang-nuts/c/Gze1TRtdLdc/ and there is
much disagreement and no clear resolution. (The initial question is not
exactly yours, but if I understand correctly, the discussion quickly gets
s
Hi!
I would like to receive clarifications, if possible, on Go memory model
guarantees about non-atomic load and stores when intermixed with atomic load
and stores.
I'm reviewing a piece of code which, simplified, works as follows:
- There is a single "writer" goroutine which
- Allocates a
On Sat, Oct 29, 2022 at 02:54:48PM -0700, Robert Solomon wrote:
[...]
>>> On ubuntu 22.04, I would like the walk function to NOT follow symlinks to
>>> other filesystems. The find command uses the -xdev switch to achieve
>>> this.
>>>
>>> How can I get walk to behave like the -xdev switch to fin
15 matches
Mail list logo
