[go-nuts] Re: slice of pointer of struct vs slice of struct

2017-10-20 Thread Feby Tanzil
hmm, suppose I have struct X that have 50 attributes that represent 50 cols in db, struct Y 4 attributes, 4 cols and I have : func FindX() *X {} func FindXs() []*X {} func FindY() *Y {} func FindYs() []*Y {} I don't care about mutable, since this is only a getter func, or should I care? sinc

[go-nuts] Re: slice of pointer of struct vs slice of struct

2017-10-20 Thread Feby Tanzil
eels too large, it's also too large for the receiver. > On Friday, 20 October 2017 12:25:27 UTC+7, Feby Tanzil wrote: > > Hi, > > I got vague answers in the internet over this. > Which is better & preferable in Go? > > type T struct { > // some attributes > ...

[go-nuts] slice of pointer of struct vs slice of struct

2017-10-19 Thread Feby Tanzil
Hi, I got vague answers in the internet over this. Which is better & preferable in Go? type T struct { // some attributes ... } func a() []T { } func b() []*T { } Thanks -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe fr