将字符串值转换为函数调用

I want to specify a function based on a string. I'm getting strings out of a map, in the example below they are the values in function while interating ove the map. Now for example, when the string value function == "networkInfo", I would like to "treat" that value as a real functions' name. It's hard to explain, but I think you guys will know what I mean.

My goal is to remove the switch statement and directly call c.AddFunc(spec, func() { networkInfo() }) where networkInfo is the function name, extracted from string function. I know this is possible, but I don't know how :(. Help is appreciated!

// ScheduleCronjobs starts the scheduler
func ScheduleCronjobs() {

tasks := props.P.GetStringMapString("tasks")
log.Infof("number of tasks: %d", len(tasks))

if len(tasks) != 0 {
    c := cron.New()

    // for each task, initialize
    for function, spec := range tasks {
        switch function {
        case "networkInfo":
            c.AddFunc(spec, func() { networkInfo() })
        case "bla":
            c.AddFunc(spec, func() { bla() })
        default:
            log.Errorf("unknown task: %q", function)
        }
    }
    c.Start()
}

// after initialization, send out confirmation message
slack.SendMessage("tasks initialized", props.P.GetString("channel"))
}

Why not something like:

taskDefs := map[string]func(){
  "networkInfo": networkInfo,
  "bla": bla,
}

for function, spec := range tasks {
  if fn, ok := taskDefs[function]; ok {
    c.AddFunc(spec, func() { fn() }) // not sure if you need the enclosing func
  } else {
    log.Errorf("unknown task: %q", function)
  }
}

If you do need varying signatures of your funcs then you'd actually need reflection, but if the types of the funcs are all the same, then using this map approach might be a simpler solution, without the overhead of reflection.

The only way I've found to find functions by name in a package is by actually parsing the source files. This repo is an example of finding funcs and storing them in a map with the name as the key.

The Go linker will silently drop unreferenced funcs, so if the only way you're referencing the func is through reflection it would break. That is why the map approach I suggest is superior; it let's the linker know the func is being used.