whoops, I misread :) types.Type,, not reflect :) On Sat, Dec 14, 2019 at 6:54 PM Axel Wagner <axel.wagner...@googlemail.com> wrote:
> https://play.golang.org/p/pdjKMn__ufA > > On Sat, Dec 14, 2019 at 10:07 AM Dan Kortschak <d...@kortschak.io> wrote: > >> 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 >> >> -- >> 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. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/golang-nuts/4fb681518e2e36e0d0564394546dd7879dd8f96a.camel%40kortschak.io >> . >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAEkBMfGmL2u_9P%2B7%2BHou%2BAP_SgPr3TKEOG4ab%3DyfpFzmi9F3tQ%40mail.gmail.com.
