Nevkontakte

That makes sense, thanks. I see you are still updating this PR. Please let me know when it is ready for a detailed review, and I'll try to do it...

And thank you again for yet another contribution to GopherJS! ☺

I am now beginning to second-guess the wisdom of the approach I've described above... On one hand it does the benefit of the smallest possible output size, which is important....

@paralin in our user survey output file size is by far the biggest pain point: So it's hard for me to argue that it isn't that important. In general it's...

@paralin no worries, that's a reasonable question to ask :) I think Google Closure Compiler is one of the most advanced JS optimizers around, but I don't think many people...

"Wrapped" types are going to be one of the bigger challenges... ### Background: Normal, non-wrapped types are represented at runtime by JS objects created by gopherjs-generated constructor functions. For example:...

Another gotcha I've discovered (although I don't have time to document it in as much detail as it deserves) is that the object representing a struct is also treated as...

I keep discovering fascinating details about GopherJS's type representation. Above I mentioned that a struct and a pointer to a struct are the same thing. Well, this isn't quite true....

I think I found a solution to the wrapped types problem: https://github.com/nevkontakte/gopherjs/commit/776d188ca55625452195d979a161e327bc902d34. I am not sure it covers 100% of edge cases, but it seems to hold up for the...

I'm kind of inclined to say "gopherjs just was head of the curve" and leave it be :) While technically it is a deviation from the Go spec prior to...