Dmitri Shuralyov

@hajimehoshi Help with maintaining this project would be greatly appreciated, thanks for the offer. I'll want to discuss it in more detail with you on Slack, hopefully soon. But first...

Thanks for reporting Andrew. I can reproduce. I've looked into it a little and I have a fairly good suspicion of what's causing this. At first, I thought it might...

I tried it by doing `gopherjs build --tags=appengine`, but it looks like gogo doesn't actually have a complete implementation in `pointer_reflect.go` compared to `pointer_unsafe_gogo.go`. I got errors like: ``` $...

> "You can't use unsafe." I think this can be detected at compile time. > > Is it possible to make the diagnostics better? You're not the first person that...

> Ugh, I didn't notice that gogo had somehow snuck into my GOPATH workspace. `goimports`, maybe? **Edit:** Ah, never mind, you said "into GOPATH workspace", not "into my .go file"....

In order to resolve this issue, we want to detect when unsafe is imported (even if indirectly). Suppose that's done, what would be ideal next step? Should GopherJS print a...

I would likely object to adding a new flag; let's try to find a solution for this that doesn't require adding flags. I see your point, we could treat "unsafe"...

Valid issue (I can reproduce), but lower priority since it concerns behavior of compiling invalid Go code (so the expected behavior is printing an error message). Thanks for catching and...

Thanks for reporting, that looks like a bug in the type system. /cc @neelance

As already discovered before, commenting out `Float32Array` and `Float64Array` cases in `$nativeArray` (causing `Array` to be used instead) increases the performance significantly in this case. ``` JavaScript var $nativeArray =...