Typical soul-sucking bike-shedding disaster of an es-discuss thread https://esdiscuss.org/topic/extensible-destructuring-proposal …
-
-
Replying to @swannodette
.
@swannodette Agreed. I really like this proposal. We were able to move from assuming Array to GetIterator(obj), this seems similar in form.1 reply 1 retweet 8 likes -
Replying to @leeb
@leeb@swannodette Also agreed. I'm curious: Is there any sensible way to polyfill this? Does anyone polyfill for iterators now?1 reply 0 retweets 0 likes -
-
Replying to @leeb
@leeb Ah, seems like `loose` mode affects it: https://babeljs.io/repl/#?experimental=true&evaluate=true&loose=false&spec=false&code=var%20%5Bx%2C%20y%5D%20%3D%20point%3B … - I wonder what perf impact is.1 reply 0 retweets 0 likes -
Replying to @BrandonBloom
@BrandonBloom Once/if Flow integration lands these types of things could be compiled with blazing compiled code performance@leeb1 reply 0 retweets 2 likes -
Replying to @BrandonBloom
@BrandonBloom Combine strict types with inference and you've got an accurate representation of types and data structures in your code@leeb1 reply 0 retweets 1 like -
Replying to @BrandonBloom
@sebmck@leeb Conservative analysis for un-annotated functions would have to infer map-like, not object-like. Unless can specialize at call1 reply 0 retweets 0 likes
@BrandonBloom You'd deopt on polymorphic code to a runtime check so that's not an issue. @leeb
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 