[go-nuts] Re: Confusion between Pointer or No Pointer for Nested array struct

2018-08-19 Thread Tamás Gulácsi
> type User struct { > ID string > Name string > Location loc > } > *Considering the situation, I do not have to change data for Owner or > Player after creating value for Games above and Player can sometimes remain > Nil, should I use only User or it's better to use *User* > > > I

Re: [go-nuts] internal compilation error while compiling gccgo from source solaris 10

2018-08-19 Thread Ian Lance Taylor
On Sun, Aug 19, 2018 at 9:47 AM, Amandeep Gautam wrote: > I have been trying to install GCCGO on Solaris 10 with the following script: > > dir=/export/home/amandeep > srcdir=$dir/gccgo-src > objdir=$dir/gccgo-obj > prefix=/usr/gnu > > > # Create Directory > mkdir -p $objdir > sudo mkdir -p

[go-nuts] Confusion between Pointer or No Pointer for Nested array struct

2018-08-19 Thread R Sharma
I have a list of users and I am finding a hard time to understand which approach is better and faster for the purpose of nesting array struct of users inside another struct. For an example - type loc struct { Type string Point []float64 } type User struct { ID string Name

[go-nuts] [Bug?] Error when running "go tool cover" on package name contains dot

2018-08-19 Thread Dave Cheney
Point of clarification, the package name doesn’t contain a dot, that is not permitted by the syntax of the package declaration. The name of the directory you placed the file in ends in .go and this is confusing the tool. If this is a regression from an earlier version of Go, please raise an

[go-nuts] internal compilation error while compiling gccgo from source solaris 10

2018-08-19 Thread Amandeep Gautam
I have been trying to install GCCGO on Solaris 10 with the following script: dir=/export/home/amandeep srcdir=$dir/gccgo-src objdir=$dir/gccgo-obj prefix=/usr/gnu # Create Directory mkdir -p $objdir sudo mkdir -p $prefix # Exports export

[go-nuts] [Bug?] Error when running "go tool cover" on package name contains dot

2018-08-19 Thread Shulhan
Running "go tool cover" on package name contains dot with Go 1.11rc1 or latest dev on branch master return an error, but success on Go 1.10.3. Steps to reproduces - Create package name with dot ('.'). - Create minimal test file - Generate test coverage profile, go test -count=1