The two are rather separate. The only way I can see combining them is if there is extensive server side template-ing. But angular.js kind of discourages that. So you can use go to build a RESTful server and then use angular.js on the front end. But that sort of de-couples the system to the point where it doesn't make sense to talk about an advantage of a combination of both.
Having myself written such a site (http://www.goread.io/), I concur. Having go on the backend didn't provide any benefits with an angular frontend over another language. I just think they excel at their respective purposes - that's why I chose them.
