On 2 February 2016 at 23:45, Michael Hudson-Doyle <michael.hud...@canonical.com> wrote: > TBH, I'm a bit vague about what problems exactly this bug actually > caused (even though I spent half a week fixing it!). So I guess that's > a shrug from me -- if it's not causing active problems and 1.6 is, as > you say, around the corner, I'd just as soon leave it out.
Cool, fair enough! Let's plan to circle back for Go 1.6 then. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
