> 2. Go isn't too deeply invested in compilation as means for catching errors. Except when you've imported a package you're not currently using, that is a mort

> 2. Go isn't too deeply invested in compilation as means for catching errors. Except when you've imported a package you're not currently using, that is a mortal sin :)