On Tue, Feb 21, 2017 at 11:56 AM, peterGo wrote:
> Will,
>
> "it looks like the plan is to fix this in Go 1.9 rather than 1.8.x, is that
> the case? " What makes you think that?
>
> https://github.com/golang/go/issues/19151: Milestone Go1.8.1
>
> https://github.com/golang/go/issues/19133: Mileston
Will,
"it looks like the plan is to fix this in Go 1.9 rather than 1.8.x, is that
the case? " What makes you think that?
https://github.com/golang/go/issues/19151: Milestone Go1.8.1
https://github.com/golang/go/issues/19133: Milestone Go1.8.1
Peter
On Tuesday, February 21, 2017 at 5:41:25 AM
On Mon, Feb 20, 2017 at 8:23 PM, Ian Lance Taylor wrote:
> On Mon, Feb 20, 2017 at 12:06 PM, Will Newton wrote:
>> On Thu, Feb 16, 2017 at 9:01 PM, Chris Broadfoot wrote:
>>> Hello gophers,
>>>
>>> We just released Go 1.8.
>>>
>>> You can read the announcement blog post here:
>>> https://blog.
Hey Will, it might help to get timings for just -race and
-coverprofile (not both) to try to isolate timing increase a bit.
On Mon, Feb 20, 2017 at 12:23 PM, Ian Lance Taylor wrote:
> On Mon, Feb 20, 2017 at 12:06 PM, Will Newton wrote:
>> On Thu, Feb 16, 2017 at 9:01 PM, Chris Broadfoot wrote:
On Mon, Feb 20, 2017 at 12:06 PM, Will Newton wrote:
> On Thu, Feb 16, 2017 at 9:01 PM, Chris Broadfoot wrote:
>> Hello gophers,
>>
>> We just released Go 1.8.
>>
>> You can read the announcement blog post here:
>> https://blog.golang.org/go1.8
>>
>> You can download binary and source distribut