Nevkontakte

@KiddoV only that it will happen at some point. I am currently writing a guide for how to add new Go version support in a hope that someone from community...

In a hope to inspire more contributions I wrote a guide to supporting new Go versions in GopherJS. I would appreciate feedback on what may be unclear (especially to the...

@omar391 starting with 1.18 version, GopherJS builds standard library in the same way that Go WebAssembly does, and these constants are [unavailable](https://pkg.go.dev/syscall?GOOS=js#pkg-constants) there. That said, to my knowledge GopherJS never...

I think you might be mixing up a few different things, so let me try and clarify. - `syscall` and `syscall/js` packages are completely different API serving different purposes, they...

That's an interesting idea, although I don't know how soon we will upgrade to ES 2017. However, ES 2015 introduced [for-of and iterable protocol](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Iteration_protocols#the_iterable_protocol), so I wonder if we can...

@tomconnell-wf I understand your enthusiasm for performance improvements and, to some degree, share it. However, hear me out 🙂 GopherJS has claimed ES5 compatibility for ages (even though in some...

@tomconnell-wf fair enough. Spare time is something we all have precious little of. Your suggestions and contributions are appreciated nevertheless 🙂

This would be great to do, even for `compiler/natives` only. Having to regenerate the VFS every time is kind of tedious and `natives` are changed a lot more frequently than...

Can you give an example when this would be necessary? In general, it seem to me that this would encourage [monkey patching](https://en.wikipedia.org/wiki/Monkey_patch), which is often fragile and is a source...

Actually, I think I may have misunderstood the intent of this PR. It allows you to make an unexported method from a third-party package available to your code, right? It...