Re: [go-nuts] Enforcing a type name rather than a variable name

2020-01-04 Thread Jan Mercl
On Sat, Jan 4, 2020 at 12:28 AM wrote: > > Hello, > > Is there any way to avoid the compilation error "*error is not a type" of > this example https://play.golang.org/p/gWNStGSCfTm ? > I understand the variable named `error` hides the type named `error` but is > there some other syntax to

[go-nuts] Enforcing a type name rather than a variable name

2020-01-03 Thread julio
Hello, Is there any way to avoid the compilation error "*error is not a type" of this example https://play.golang.org/p/gWNStGSCfTm ? I understand the variable named `error` hides the type named `error` but is there some other syntax to specify the error type? I am facing this issue while