types lookup for error interface type

[Dan Kortschak]

In the go/types package there is an easy way to obtain a types.Type for
basic builtin types. This doesn't exist for the error type.

Is there an easier way to get a types.Type representing error than by
using NewInterfaceType, NewFunc and NewSignature functions (I am
assuming that the nil *types.Package is what should be used for the
call to NewFunc).

thanks
Dan

[Marcin Romaszewicz]

Error is an interface, so its type depends on the implementation satisfying that interface. You can't just create an "error", since they don't exist, all that exists are implementation satisfying the error interface. That's what you're doing with NewSignature.

Could you just create an implementation of the error interface and instantiate one of those?

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/4fb681518e2e36e0d0564394546dd7879dd8f96a.camel%40kortschak.io.

[Axel Wagner]

https://play.golang.org/p/pdjKMn__ufA

[Axel Wagner]

whoops, I misread :) types.Type,, not reflect :)

[Dan Kortschak]

I think I must have asked this really badly.

I don't want a reflect.Type of an error, I want a types.Type
representation of error for performing static analysis.

The playground that I imagine is necessary is something like this.

https://play.golang.org/p/e-FU0_4J9jK

This seem massively over complicated, so I'm wondering if there is an
easier way.

[Paul Jolly]

> This seem massively over complicated, so I'm wondering if there is an
> easier way.

I think you're after types.Universe.Lookup("error")?


Paul

[Dan Kortschak]

I think you are right. Thanks.