On Thursday, August 27, 2020 at 11:38:54 PM UTC-7, Johann Höchtl wrote:
>
>
> Since long I am keeping my go installation up to date by compiling from
> source. Today on my attempt to update from 1.14.4 to 1.15 I triggered this
> fatal:
>
>
> GOROOT_BOOTSTRAP=/home/john/opt/go.build/
On Wednesday, June 17, 2020 at 5:50:24 PM UTC-7, Ian Lance Taylor wrote:
>
> On Wed, Jun 17, 2020 at 9:36 AM Charles Crete > wrote:
> >
> > Based on the new proposal, having the type parameters as () seems very
> confusing, as now 3 things in a row use ():
> > - Type parameters
> > -
On Wednesday, June 10, 2020 at 1:03:41 PM UTC-7, joe mcguckin wrote:
>
> I read somewhere that the default # of GO threads is the number of cores
> of the cpu.
>
> What about where there are multiple cpus? My servers have 2, 6 core
> Xeons. With hyper threading, it looks like 24 cores available
I suspect it's the classic that I think everyone does at least once - in
the second code block the for loop reuses the same storage on each
iteration for the variable site. Try adding:
site := site
..just before your append to verify this.
Cheers,
-Sam.
On Thursday, June 6, 2019 at 6:49:00
There is guru (
https://docs.google.com/document/d/1_Y9xCEMj5S-7rv2ooHpZNH15JgRT5iM742gJkw5LtmQ/edit)
but it's intended for editors not humans. I suppose that means perhaps
you could use one of the editors that uses guru ?
Regards,
-Sam.
src/io/io.go:#5381 is where io.ReadSeeker is defined:
On Wednesday, November 21, 2018 at 2:38:42 PM UTC-8, Sun Frank wrote:
>
> Perfect! Thank you so much for your answer and explanation, : )
>
It is, unfortunately, a very common "gotcha". More discussion can be found
here: https://github.com/golang/go/issues/20733
Cheers,
-Sam.
> Best
On Thursday, October 18, 2018 at 4:28:23 PM UTC-7, Ian Lance Taylor wrote:
>
> The question is: is anybody actually doing this? Is anybody seriously
> thinking about it?
>
> Ian
>
Unhelpfully, I imagine it unlikely that anyone distributing binary go
packages reads golang-dev or golang-nuts.
