I did a git pull. There is a tag go1.13.1, but no tag go1.13.2. Also, no
tag go1.12.11.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@g
Katie Hockman once said:
> The Go 1.13.2 release also includes a fix to the compiler that prevents
> improper access to negative slice indexes in rare cases. Affected code, in
> which the compiler can prove that the index is zero or negative, would have
> resulted in a panic in Go 1.12.11, but cou
On Fri, Oct 18, 2019 at 4:59 PM Anthony Martin wrote:
>
> Katie Hockman once said:
> > The Go 1.13.2 release also includes a fix to the compiler that prevents
> > improper access to negative slice indexes in rare cases. Affected code, in
> > which the compiler can prove that the index is zero or