@cadey Isn't this supposed to be one Go's greatest strengths? Forcing me to deal with errors when they occur rather than abstracting away makes for good error logging and easier debugging in my experience.

@bfiedler Yes but sometimes you just want to write complicated things without having to write 37 instances of if err != nil in a row

Sign in to participate in the conversation
Interlinked MST3K

this is mst3k