Nevkontakte

Heads-up to anyone following this issue, I have rebased the `generics` branch on top of the latest mater and force-pushed it into the repository. If you have it checked out,...

@timdp you don't need to use my fork, everything that's in a semi-working condition is merged into the `generics` branch in this repo. So `go install github.com/gopherjs/gopherjs@generics` should work. However,...

@timdp yep, that's an error I'd expect to happen until operator support is implemented. That's the major missing piece right now. If you are in a hurry and wasm is...

I guess now would be a good time for a small confession... The longer I've been working on a generics implementation I described [here](https://github.com/gopherjs/gopherjs/issues/1013#issuecomment-1217237123), the less happy I was with...

@flimzy how do you feel about merging the `generics-ng` branch into master in its current state, gating generics support behind some sort of `GOPHERJS_EXPERIMENT` flag? Generics are not production-ready yet,...

I think this is obsolete as of https://github.com/gopherjs/gopherjs/pull/1111.

Fun fact: apparently, channels are already implemented according to the principle proposed here.

That looks like a bug in pointer internalization. Here it seems to only handle pointers to structs: https://github.com/gopherjs/gopherjs/blob/fbc70fee0b646e68ae0ecfe4bfef7ddf359cbf45/compiler/prelude/jsmapping.js#L330-L332C14 Moreover, there is no break, so it probably falls through to the...

Unfortunately, no. Pointers in GopherJS are kind of weird and have a lot of special cases (which is probably why they aren't handled properly here). For example, structs and pointers...

As always, your contribution will be very welcome. If I were to do this, my goal would be to understand how pointers to different types are working (e.g. ints, strings,...