> Ian mentioned that "Google" as a company doesn't actually choose to do a
> lot. The Go team is largely autonomous in their decision making and isn't
> being influenced by executives.
> So, to put it another way: If the only role the company plays is to
> provide paychecks to some Go develope
Jan's comments about possible outcomes other than those outlined in
Sotirios' second post are correct. Using atomic.Value would synchronise
the values due to the introduction of a write barrier. I'm not omitting
much of the argument, you're just missing it.
Sorry, I'm done.
On Mon, 2019-05-27 at
You have conveniently omitted much of the argument, for example, like reading
Ander from a string containing Anderson due to improper synchronization - which
is clearly incorrect and what I was pointing out. The java refs are important
to this discussion since when everything is ref and under GC
On Tue, May 28, 2019 at 1:08 AM Matt Farina wrote:
> Three things I've considered:
>
> 1) when a company runs a project without much publicly documented process
> but does as they choose, isn't that a sign of a company run project?
>
Ian mentioned that "Google" as a company doesn't actually choo
In the post that I was replying to you told the OP to ignore incorrect
comments and then brought in the java world and stated that
synchronisation was not needed, only atomic operations. The comments by
previous posters were not incorrect and how things work in java is only
barely relevant here giv
>
>
>> I'm not sure whether I agree with this characterization. There is, AFAIK,
> approximately no codified process in the Go project that would single out
> Google or Google Employees. To a degree, that's because there aren't that
> many codified processes and the ones there are, are kept a bit v
Hi,
Please check out this implementation of idea that I had: It allows a
constant access-time for the context values for the most common use-case.
(The standard library access time is linear with the number of values in
the context).
I'd appreciate your feedback.
https://github.com/posener/fc
On Mon, May 27, 2019 at 2:18 AM Sergey Kamardin wrote:
>
> On Sun, 05/26/19, May 26, 2019 at 07:59:07PM -0400, Ian Lance Taylor wrote:
> > This is not valid. The rule is that SliceHeader is only valid when
> > inspecting an actual slice header. You have to write
> >
> > h.Data = uintptr(unsa
On Mon, 27 May 2019 12:31:22 -0700 (PDT)
Liam wrote:
Rust was irreparably damaged by delivering custom painted ponies to the
most vocal and enough stubborn "representatives of the whole community".
I personally wishes Go team will guard the future of Go free from such fate,
as they did for past
On Mon, May 27, 2019 at 9:16 PM Matt Farina wrote:
> This whole conversation illustrates the difference between open source and
> open governance. Go is open source but the governance is controlled by
> Google. This compares to something like Kubernetes that is both open source
> and open governa
On Mon, May 27, 2019 at 1:35 AM Axel Wagner
wrote:
>
> This is a bit of an aside, I agree with everything Ian said, but:
>
> On Thu, May 23, 2019 at 7:59 PM Ian Lance Taylor wrote:
>>
>> If a language is to change over time, this specification or
>> implementation must change. Somebody has to de
On Thu, May 23, 2019 at 8:50 PM wrote:
>
> Ian: I find many of your comments related to how the Go team functions very
> interesting,
> I for one would find it helpful if 2 or 3 times a year the Go Team would
> communicate to the Go community at large, information related to where and
> in wha
I’m sorry if you think I put words in your mouth, I did not mean to.
Can you please explain what "Please don’t” means then? I took it at face value,
and that it was a affirmative response to “Don’t be clever."
> On May 27, 2019, at 7:33 AM, Dan Kortschak wrote:
>
> Please don't say I've said t
I filed an issue requesting that the Go team issue RFPs to both communicate
directions they plan to go in, and solicit community input about them. It
was declined.
proposal: Go 2: establish RFP/RFC process for language feature proposals
https://github.com/golang/go/issues/29860
Part of my reaso
This whole conversation illustrates the difference between open source and open
governance. Go is open source but the governance is controlled by Google. This
compares to something like Kubernetes that is both open source and open
governance.
Should Go be open governance? It sounds like this is
https://2019.www.torproject.org/docs/tor-onion-service.html.en
free, no cc required.
On Monday, May 27, 2019 at 8:01:38 PM UTC+2, aimar wrote:
>
> Hi,
>
> My teacher has asked me to develop an API with Golang and test it on the
> web instead of localhost. I was thinking of github.io but then I f
On Mon, May 27, 2019 at 8:01 PM aimar wrote:
> Would you please let me know, if there is any platform which I can test my
> API online rather than localhost? (for free, of course)
GCP free tier?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
Hi,
My teacher has asked me to develop an API with Golang and test it on the
web instead of localhost. I was thinking of github.io but then I figured
out, it doesn't support server-side languages and just support static
pages. Would you please let me know, if there is any platform which I can
Please don't say I've said things I didn't. I did not dissuade someone
from understanding or using something. I quoted the memory model, and I
pointed out that the advice given by previous posters was not incorrect
as you claim. What you are reading them as saying may be wrong, but not
what they ar
They are not clever. They are foundational in high performance lock-free
structures and other techniques commonly found in HPC and HFT - and even the
linux kernel (RCU). This is a decent overview
https://www.cs.cmu.edu/~410-s05/lectures/L31_LockFree.pdf but a bit hard to
follow since it is sli
The actual organizational structure of Debian is pretty complex. You can
think of Debian Developers (DD) as "people who can submit to Debian" (so
the people with approval rights in gerrit, in analogy to the Go project).
The people who steer the project and are final deciders on Debian (so the
"core
So, I'm creating a package for my service. Let's say I have multiple
versions with different features depending on the version and authorization
type specified, such as:
Authorization Type: ThirdParty
Version: 1.0
Utilizes: HMAC_SHA1 hash digest
Authorization Type: ThirdParty
Version: 1.1
Util
Debian users vote for someone to become Debian Developer and give him right
to vote? If no, how can it be "representative"?
пн, 27 мая 2019 г. в 08:35, 'Axel Wagner' via golang-nuts <
golang-nuts@googlegroups.com>:
> This is a bit of an aside, I agree with everything Ian said, but:
>
> On Thu, M
On Mon, 27 May 2019, 07:18 Sergey Kamardin, wrote:
> Hello Ian,
>
> Thank you for your answer.
>
> On Sun, 05/26/19, May 26, 2019 at 07:59:07PM -0400, Ian Lance Taylor wrote:
> > This is not valid. The rule is that SliceHeader is only valid when
> > inspecting an actual slice header. You have t
24 matches
Mail list logo