Checker.Check() should return error, not (bool, string); would match Go idioms better

Bug #1123659 reported by Tv
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gocheck
New
Undecided
Unassigned

Bug Description

Right now, I need to do a lot of

  ..., err := something()
  if err != nil {
    return false, err.Error()
  }
  return true, ""

That is ugly for several reasons, including needing the empty string. Gocheck seems to be from an era where os.Error still existed (http://labix.org/gocheck shows os.Errno in example). Check() could just return a single err, and nil would mean success.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.