You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
be better than using Object.create in your example
videos.reduce(function(accumulatedMap, video) {
// Object.create() makes a fast copy of the accumulatedMap by
// creating a new object and setting the accumulatedMap to be the
// new object's prototype.
// Initially the new object is empty and has no members of its own,
// except a pointer to the object on which it was based. If an
// attempt to find a member on the new object fails, the new object
// silently attempts to find the member on its prototype. This
// process continues recursively, with each object checking its
// prototype until the member is found or we reach the first object
// we created.
// If we set a member value on the new object, it is stored
// directly on that object, leaving the prototype unchanged.
// Object.create() is perfect for functional programming because it
// makes creating a new object with a different member value almost
// as cheap as changing the member on the original object!
var copyOfAccumulatedMap = Object.create(accumulatedMap);
copyOfAccumulatedMap[video.id] = video.title;
return copyOfAccumulatedMap;
},
// Use an empty map as the initial value instead of the first item in
// the list.
{});
The text was updated successfully, but these errors were encountered:
So I think the conclusion on this issue, from this conversation, was that we want exercise 19 to work with immutable data. As one person said, "mutating the original copy through out the call stack would be considered a 'side effect' and not very 'functional.'"
Your solution is more performant, testable, and simple. In an interest to achieve the most value I submitted this pull request which uses Object.assign() instead of Object.create().
Hi wouldn't this code for reduce
be better than using Object.create in your example
The text was updated successfully, but these errors were encountered: