ES6 modules & destructuring don't match. If `import foo from 'foo'` and `foo.bar` exists, no guarantee I `import { bar } from 'foo'` does.
-
-
Replying to @_jayphelps
@_jayphelps Are you assuming that `{` means destructuring? We intentionally used a different syntax `foo as bar` to make it clear it's diff3 replies 0 retweets 1 like -
Replying to @_jayphelps
@wycats I wish it didn't exist and import foo from "foo" would import all the named exports. If it did, you could destructure if you want2 replies 0 retweets 0 likes -
Replying to @_jayphelps
@_jayphelps example: `bind` is a property on functions but also a named export of underscore. Worlds collide.2 replies 0 retweets 2 likes -
Replying to @BenLesh
@BenLesh @_jayphelps the core issue is just that objects already have a bunch of stuff on them, and people want to use them as defaults
6:43 PM - 18 Mar 2015
0 replies
0 retweets
0 likes
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.