hopefully there are no naming collisions with MooTools :)
-
-
-
Too soon!
End of conversation
New conversation -
-
-
There was a task where it would have been really handy for me and wanted to propose it as well. Unfortunately when I looked up it was already submitted for a weeks.
But I am really looking forward for it! 
-
Coming to
@v8js and Chrome soon :) (It’s already available behind the --harmony flag!)
End of conversation
New conversation -
-
-
Awesome! Thank you for proposing this! What are the best ways to show support for
@TC39 proposals? -
Don’t thank me — thank
@bakkoting and@ljharb! Your support has been noted. Based on the reactions to this tweet, there seems to be widespread support. - 2 more replies
New conversation -
-
-
My initial thought is that this doesn't really do much other than offer sugar over: entries.reduce((x, [k, v]) => (x[k] = v, x), {}) I don't run into this problem a lot so maybe someone could suggest an example where a native language feature is needed?
-
The repository I linked to has some examples. You’re right that this is currently possible, but having it as a built-in static method would greatly reduce¹ friction. ¹ See what I did there?
- 4 more replies
New conversation -
-
-
yay! I keep doing Object.entries().reduce(fn, {}) so, that’d be an amazing thing to have!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This is great. I made a library for this a few years back (https://github.com/ckknight/object-from-entries …) and would love to see this become a standard.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.
New ECMAScript proposal to add Object.fromEntries, complementing Object.entries: