It was one of my first thoughts, too. So, just for those who haven't tried it... it does work, technically -
&{200 OK 200 HTTP/2.0 2 0 map[Cache-Control:[private, max-age=0] Content-Type:[text/html; charset=ISO-8859-1] X-Xss-Protection:[1; mode=block] Set-Cookie:[NID=88=E2yqXfl49gKoEJYEtuL4H_FOWxG0OSrOROawAQzestRQCp0dY5cBc-vtLsu-U0ZOO9YF4ZgsuLi_yXc1WoJM-l3p06bGnOghpQiX7UNFdpfO-axDIMQsKkex90z1qSYxIUghrOSUFpPYVhI; expires=Sat, 08-Apr-2017 19:32:14 GMT; path=/; domain=.
google.com; HttpOnly] X-Frame-Options:[SAMEORIGIN] Alt-Svc:[quic=":443"; ma=2592000; v="36,35,34,33,32"] Date:[Fri, 07 Oct 2016 19:32:14 GMT] Expires:[-1] P3p:[CP="This is not a P3P policy! See
https://www.google.com/support/accounts/answer/151657?hl=en for more info."] Server:[gws]] 0xc420399200 -1 [] false true map[] 0xc4203300f0 0xc4202e6840}
However, for useful output, you'd really want to show the body. The problem is that it requires a lot of understanding of how the http.Client works. If you get a 404 from the site, you'll get an empty body and no error... obviously what you'd want is to show the 404, and not just an empty body. I could just hack all that into the generator code.. and maybe that would be worth the wow factor to do it... but in general, I was hoping to avoid type-specific handling and try to be more generic so I don't have to write a new handler for every possible return type.
Maybe a workable heuristic would be - if the return type has a field that is an io.Reader, try to read that reader. If it's not empty, show that data, otherwise, just print the struct. That's kind of a hack... I wonder how many other return values would actually follow that pattern.