Jonathan Hall

Would it be possible to override that behavior some how, (command line flag?) to permit the knowing compilation of such code, if the "unsafe" behavior is non-essential? OTOH, although Go...

I do prefer the Go philosophy of aborting a compile rather than warning. However, as GopherJS is a port, it doesn't have the same power to make the "best" design...

That can work when I am writing the tests. But when wrapping third-party tests, I don't have that level of control.

I have put up a prototype of something like what I have in mind here: http://aslan.flimzy.com/~jonhall/tests/ (warning: it will likely hang your browser tab for several tens of seconds on...

> I think the official recommendation it to create a source tools.go somewhere We can go one step further, and put it in a subdir so that its in its...

> Is there something special I need to do to include reflect changes? I believe this is probably what you're looking for: https://github.com/gopherjs/gopherjs/wiki/Developer-Guidelines#code-generation

I have been able to reproduce this all the way back to GopherJS 1.12-1, so this does not appear to be caused by using the new GOPHERJS_ROOT configuration, for what...

This one has me really stumped. I've attempted to go back to code I knew was working in the past, with an old version of GopherJS, and the problem is...

> I've tried to reproduce your issue at current master and I noticed an interesting behavior: Thank you for taking the time! I've noticed a number of other gopherjs caching...

This looks like it may be related to, if not identical to, #402.