News for hackers. Stuff that matters.
Re:Go 2.0 Error Handling Requirements by ben_jones on Sunday October 14, 2018 @08:49PM (#18216583)
A nifty code snippet I use for this:

  // ErrLine returns an error formatted to include the line 
  // number of where it occurred (presumably with a performance penalty)
  func ErrLine(err error) error {
    if err != nil {
      // notice that we're using 1, so it will actually log the where
      // the error happened, 0 = this function, we don't want that.
      pc, fn, line, _ := runtime.Caller(1)
      err = fmt.Errorf("[error] in %s[%s:%d]: %s", 
      runtime.FuncForPC(pc).Name(), fn, line, err.Error())

    }

    return err
  }
Re:Go 2.0 Error Handling Requirements by stouset on Sunday October 14, 2018 @10:25PM (#18217004)
Edit: I misread this comment. Apologies.
Re:Go 2.0 Error Handling Requirements by fierro on Sunday October 14, 2018 @11:11PM (#18217156)
yes, why use a function