On Sun, Jul 3, 2016 at 11:57 PM, Gordon Klaus <gordon.kl...@gmail.com> wrote:
> Ok, so strictly speaking there is no bug.  Both gc and gccgo are
> spec-compliant; gc just opts not to raise an error in this case.  (One might
> say it is a bug that gc doesn't raise the error consistently, but I don't
> think the spec says anything about consistency, only optionality.)

I think it is a bug in the gc compiler, and that bug is
https://golang.org/issue/3059 .

Ian

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to