On Fri, May 20, 2016 at 11:54:58AM +1200, Michael Hudson-Doyle wrote: > FWIW my impression is that this issue has been addressed upstream and will > be fixed in the 1.7 release, but maybe someone should check?
According to https://github.com/golang/go/issues/13247 this issue has been fixed in commit 5bbb98df0960f57dca73cb7640456608d4cc0917. Peter
