#####   ######  #####    ###    #   #  ###  #   #  ######
##  ##  ##      ##  ##  ## ##   #   #   #   #   #  ##
#####   ####    #####   #   #   #   #   #   #   #  ####
##  #   ##      ##      ## ##    # #    #    # #   ##
##   #  ######  ##       ###      #    ###    #    ######

$ curl repovive.com/roadmaps/go/error-handling/don-t-ignore-errors

░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░██████████████████████████████████████████████████████████████████

#####   ######  #####    ###    #   #  ###  #   #  ######
##  ##  ##      ##  ##  ## ##   #   #   #   #   #  ##
#####   ####    #####   #   #   #   #   #   #   #  ####
##  #   ##      ##      ## ##    # #    #    # #   ##
##   #  ######  ##       ###      #    ###    #    ######

$ curl repovive.com/roadmaps/go/error-handling/don-t-ignore-errors

Repovive

Don't Ignore Errors - Error Handling | Go | Repovive

Repovive.

Go10 sections · 431 units20h total

Open in Course

Don't Ignore Errors

A critical rule

Never silently ignore errors:

// Bad: error ignored
result, _ := riskyOperation()

// Good: error handled
result, err := riskyOperation()
if err != nil {
    log.Printf("warning: %v", err)
}

If you must ignore an error, at least log it. Silent failures create bugs that are hard to diagnose.