On Wed, Dec 19, 2018 at 7:37 AM Miroslav Němec <ne...@vshosting.cz> wrote: > > I have an example of uncompilable code here - > https://play.golang.org/p/yIYEa1YcQfs , compiler wrongly identifies type of > A.c . > > I can go around the issue when I move newA function below type definitions > https://play.golang.org/p/jLh2fYBu5mc . > > Is this a compiler issue, or does really type/func declaration order matter?
I think it's a bug. gccgo compiles your code as expected. With Go1.12beta1, the gc compiler crashes. Please report this at https://golang.org/issue. Thanks. 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.
