As far as I'm concerned, `defer resp.Body.Close()` is perfectly cromulent and there's no need to for error checking contortions to satisfy the lint tool. If we're talking about a http.Request I doubt that the close can ever fail (I haven't checked; but it doesn't seem like something that would make sense). More generally, Close() failing on something read-only is not something I'd worry much about. If it happens systematically there's something seriously wrong with the system and you'll get errors from Open() or similar when you run out of file descriptors...
//jb
> --
> You received this message because you are subscribed to the Google Groups "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
golang-nuts...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.