[go-nuts] Re: Confusing type rules

2017-06-05 Thread conrad via golang-nuts
Thanks both! On Saturday, June 3, 2017 at 5:22:20 PM UTC-7, Xio Fen wrote: > > To answer the first point - the keyword is "*assignable*" here - an slice > []int{1,23} is not assignable to a slice []I where I is a type of int. See > https://golang.org/ref/spec#Assignability > > ( also golang tre

[go-nuts] Re: Confusing type rules

2017-06-03 Thread xiiophen
To answer the first point - the keyword is "*assignable*" here - an slice []int{1,23} is not assignable to a slice []I where I is a type of int. See https://golang.org/ref/spec#Assignability ( also golang treats slices as types in themselves ie https://golang.org/ref/spec#SliceType ) ..Howeve

[go-nuts] Re: Confusing type rules

2017-06-03 Thread Dragos Harabor
You are not alone. https://github.com/golang/go/issues/15209 On Saturday, June 3, 2017 at 4:13:03 PM UTC-7, Conrad Irwin wrote: > > Hey nuts! > > I ran into the following confusion today: > https://play.golang.org/p/XH8wyj6IbT. > > Consulting the golang spec, I think this is correct. `If the fina