Re: [go-nuts] (Un)Expected compiler behavior on named/unnamed parameters of interface functions

On Fri, Aug 11, 2017 at 11:51 AM, Penguin Enormous wrote: > My eyes has just been opened. Silly me, I get it now. Thank you very much. > > May I ask which section in the Language Specification mention this allowance > of int (or float64, ... etc.) for use as identifier

Re: [go-nuts] (Un)Expected compiler behavior on named/unnamed parameters of interface functions

My eyes has just been opened. Silly me, I get it now. Thank you very much. May I ask which section in the Language Specification mention this allowance of int (or float64, ... etc.) for use as identifier names? On Saturday, August 12, 2017 at 1:30:04 AM UTC+7, Ian

Re: [go-nuts] (Un)Expected compiler behavior on named/unnamed parameters of interface functions

On Fri, Aug 11, 2017 at 11:03 AM, Penguin Enormous wrote: > > I think that there is inconsistency in the way Go compiler report error > regarding name/unnamed parameters. This is a bit hard for me to explain in > words so please check out this short snippet first: > >

[go-nuts] (Un)Expected compiler behavior on named/unnamed parameters of interface functions

I think that there is inconsistency in the way Go compiler report error regarding name/unnamed parameters. This is a bit hard for me to explain in words so please check out this short snippet first: https://play.golang.org/p/Sg0DtCtgF2 Is this unexpected behavior or it's just me that's feeling