golang/mobile is still maintenance. If you encounter any usage issues, feel
free to report them here: https://github.com/golang/go/issues
On Monday, September 12, 2022 at 3:33:18 AM UTC+2 sytuv ccoxf wrote:
> Is golang/mobile still active?
>
> It seems like does not committed since Jul 23 2022.
ations on different memory locations obey the program statements
order within a goroutine.
On Mon, Aug 15, 2022 at 10:16 AM Axel Wagner
wrote:
>
> On Mon, Aug 15, 2022 at 10:02 AM Changkun Ou wrote:
>>
>> > The memory operations in each goroutine must correspond to
of execution. The most relaxing
requirement: permit the compiler to switch the statement.
On Mon, Aug 15, 2022 at 9:32 AM Axel Wagner
wrote:
>
>
>
> On Mon, Aug 15, 2022 at 9:06 AM Changkun Ou wrote:
>>
>> I think the new memory model does not guarantee this program always pr
I think the new memory model does not guarantee this program always prints 1:
1. There is no synchronization guarantee between line 13 and line 14
as these atomic operations are manipulated on the different memory
locations.
2. It is *not* prohibited for the compiler to switch line 13 and line
14
lot of time from a very early attempt to tackle the problem once again.
Changkun
On Tuesday, May 3, 2022 at 9:38:35 PM UTC+2 Ian Lance Taylor wrote:
> On Tue, May 3, 2022 at 12:28 PM Changkun Ou wrote:
> >
> > I wonder how the Go project defines a breaking change, specifically f
Hi gophers,
I wonder how the Go project defines a breaking change, specifically for the
case where we have an existing API but want to add ... to its parameter
list for customizations.
For instance, we have an API:
package foo
func Bar() {}
And the current code uses this function as:
foo.Bar
Hi golang-nuts,
I am trying out the latest type parameter and type sets design.
The purpose is to implement a Clamp function that works for numbers and
vectors.
The version for numbers is straightforward and easy:
```go
// Number is a type set of numbers.
type Number interface {
~int | ~int8 | ~
Many thank for the perf tool, it is pretty awesome.
> On 27. Aug 2019, at 13:36, Robert Engels wrote:
>
> Ok maybe it wasn’t the cache issue, so then try this, below a certain number
> of go routines given the workload the spin and cas works, beyond a certain
> point it is forced into the sema
