Chewxy

Note: the solution to this was to not use `Chan`, which is what I did in the current `sparse` branch. But I would still like to get to the bottom...

_From @egonelbre on August 15, 2017 10:38_ I'm getting a few compilation errors when trying to run it: ``` # github.com/chewxy/gorgonia ./op_tensor.go:958: zdvdT.Materialize undefined (type tensor.Tensor has no field or...

Yeah, that's fine.. the `gorgonia` package is still not yet fixed in the refactor. This problem is specific to the tensor subpackage (`"github.com/chewxy/gorgonia/tensor"`). The tests I refer to are the...

_From @egonelbre on August 15, 2017 12:35_ Is this intentional that `func extractPointer(a interface{}) unsafe.Pointer {` is called on a float32/float64? With small values the second data contains the actual...

That's not true since Go 1.4 right (because I recall being quite upset I can no longer stuff small values into interfaces)? Also I don't think `extractPointer` is being used...

_From @egonelbre on August 15, 2017 14:16_ Preliminary tests seem to agree with your information. There seems to be some code still about it https://github.com/golang/go/blob/964639cc338db650ccadeafb7424bc8ebb2c0f6c/src/runtime/typekind.go#L42... but I wasn't able to...

_From @egonelbre on August 15, 2017 14:48_ First interesting datapoint, changing `GOGC` (e.g. `GOGC=off` or `GOGC=50`) can make "broken" test into "working" one.

_From @egonelbre on August 15, 2017 15:2_ With `GOGC=130` I managed to get a proper segfault: ``` unexpected fault address 0xb01dfacedebac1e fatal error: fault [signal SIGSEGV: segmentation violation code=0x1 addr=0xb01dfacedebac1e...

_From @egonelbre on August 15, 2017 15:11_ `GOGC=129`: ``` unexpected fault address 0xb01dfacedebac1e fatal error: fault [signal SIGSEGV: segmentation violation code=0x1 addr=0xb01dfacedebac1e pc=0x105b0dc] goroutine 183 [running]: runtime.throw(0x18abf8f, 0x5) /usr/local/Cellar/go/1.8.3/libexec/src/runtime/panic.go:596 +0x95...

if `0xb01dfacdebac1e` is not an edited memory address, it's extremely remarkable that it errored at a human readble memory. Both these segfaults are interesting - they relate to strings and...