Sergey Rubanov
Sergey Rubanov
Oh. I though that by consensus you mean something like approvement from committee. That unshipping compatibility rule makes sense to me.
So if feature won't be approved in the time when it will be shipped in most browsers then it won't go to spec. Though browsers can't unship this feature. Probably...
There is an ASI hazard here ```js foo = gen () => {}; ```
TBH, any of `*=>`, `=>*` or `=*>` look totally fine and clear to me.
Added `generator` keyword as a possible solution to the README.md and to the first message of this issue
what about `context`?
IMO it's better to make `context` optional. Because of it's rare use. You don't need `context` if you don't have `contextTypes` for your component. BTW as I understand `updater` is...
I mean that it should be handful to omit some arguments (i.e. `state`, `context`, `updater`) if you don't need them in `render` function. Also I think order should be `props`...
Yes, I mean bridging with JS
WebAssembly doesn't have any structures besides number types. It has proposal for `anyref` though.