Go proposal: Leave “if err != nil” alone?
Go&#x27;s error handling reminds me of C or PHP error handling.  Check the status code.  Since everything can mess with that error condition, you have to be careful in how you handle it, but there is nothing forcing you to handle it.  I like exceptions because handling an error is default delegated until something wants to or can handle the error.  In the case of go, if there is a layer above your function that should process the error, you have to do that if&#x2F;err in each function that isn&#x27;t going to handle it.  I strongly believe in halting on error as the default response, and unwinding until the correct layer can proceed.