The real question from this example is: why are you creating two http requests in the same scope before using them? I've been writing Go cloud stuff for the be

The real question from this example is: why are you creating two http requests in the same scope before using them? I've been writing Go cloud stuff for the better part of a decade and "req" for a request has never been ambiguous because I go ahead and send the request and process the response before sending another one, at which point I can just reassign the variable and let the first one fall out of scope.