Chewxy

So I ran this ``` cat /dev/null > err.txt cat /dev/null > out.txt for gc in `seq 0 1 250`; do echo "======= GOGC=$gc =======" >> err.txt echo "======= GOGC=$gc...

_From @egonelbre on August 16, 2017 9:18_ `0xb01dfacedebac1e` is a poison address... see https://go.googlesource.com/go/+/17f9423

Ran this on a macbook with 1.8.3 ... can't find the poison address either. What the hell is happening?

I'm also trying to learn what the diff is between @davecgh 's [go-spew](https://github.com/davecgh/go-spew) that caused a poison address bug about a year back and how he fixed it...

_From @egonelbre on August 17, 2017 11:2_ I wasn't able to crash it with 1.9rc2 on Windows either, but I was able to get a few different values: ``` 2017/08/17...

Thanks for that bug finding. :) I'll go dick around with your example and see what happens

This is what was used for my AlphaGo reimplementation: ``` func RotateBoard(board []float32, m, n int) ([]float32, error) { if m != n { return nil, errors.Errorf("Cannot handle m %d,...

safety first, so `memmove` - i.e. allocating a new matrix fist. then a unsafe version (i.e. in place). Send PR :)

So, the `.Coord()` method is meant to be read **before** use. The docs do mention that `.Coord()` returns the **next** coordinate. This is because an `Iterator` is a data structure...

This seems to be a version issue. Which version are you getting?