Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Go reflect. How to check whether reflect.Type is an error type?

I need to assuredly check whether a reflect.Type is an error.

There is no reflect kind for error. What is the formal/idiomatic manner to check for type error in go reflect?

Go Playground Full Example

//return map of default values, based on each return type of a function
// error  => err=nil
// bool   => true
// struct => new struct
func getDefaultValue(originalFunction interface{}) map[int]reflect.Value {
    defaultValues := make(map[int]reflect.Value)

    typeOfFunc := reflect.ValueOf(originalFunction).Type()

    numOut := typeOfFunc.NumOut() //number of function returns

    for i := 0; i < numOut; i++ {

        typeOut := typeOfFunc.Out(i) // type of return for index i
        switch typeOut.Kind() {

        case reflect.Bool:
            defaultValues[i] = reflect.ValueOf(true)

        case reflect.Struct:
            defaultValues[i] = reflect.New(typeOut()).Elem()

        // --> How to identify reflect.Type error assuredly, using switch or if...
        //case reflect.error: //don't exists
        //  var err error = nil
        //  defaultValues[i] = reflect.ValueOf(&err).Elem()

        default:
            //var err error = nil
            //defaultValues[i] = reflect.ValueOf(&err).Elem()
            fmt.Println("type of return index ", i, " was not identified")

        }

        fmt.Println("type of return index ", i, typeOut, "kind", typeOut.Kind(), "assign to err ", typeOut.AssignableTo(reflect.TypeOf(errors.New(""))))
    }

    return defaultValues
}
like image 392
DLopes Avatar asked Jun 06 '15 23:06

DLopes


People also ask

How do you know if reflection is nil?

The reflect. IsNil() Function in Golang is used to check whether its argument v is nil. The argument must be a chan, func, interface, map, pointer, or slice value; if it is not, IsNil panics.

Should we use reflect in Golang?

Reflection is the ability of a program to introspect and analyze its structure during run-time. In Go language, reflection is primarily carried out with types. The reflect package offers all the required APIs/Methods for this purpose. Reflection is often termed as a method of metaprogramming.


2 Answers

In Go error is not something special. error is just a predeclared interface type so it doesn't have its own Kind in reflect. Try something along:

errorInterface  := reflect.TypeOf((*error)(nil)).Elem()
...
case reflect.Interface:
    if typOute.Implements(errorInterface)  // it's an error
like image 83
Volker Avatar answered Sep 20 '22 22:09

Volker


Create a new value of the reflected type and do a type assertion:

...
default:
    typeOutValue := reflect.New(typeOut)

    if _, ok := typeOutValue.Interface().(*error); ok {
        defaultValues[i] = typeOutValue.Elem()
    } else {
        fmt.Println("type of return index ", i, " was not identified")
    }
}

or switch on its interface type:

...
default:
    typeOutValue := reflect.New(typeOut)

    switch typeOutValue.Interface().(type) {
    case *error:
        defaultValues[i] = typeOutValue.Elem()
    default:
        fmt.Println("type of return index ", i, " was not identified")
    }

This way you can handle also any other interface type that you can (and want to) be particular about, with a more idiomatic Go code and reduced reliance on (or, at least, calls into) the reflect package (overhead and all that).

like image 32
antichris Avatar answered Sep 22 '22 22:09

antichris