Skip to content

Conversation

@davidmason
Copy link

Same as #4968 but targeting 0.13-stable in case that is a better place for it.


For $set and $apply it is cheap and easy to check whether the new value will
be identical (===) to the old value and create a new object only when this is not
the case. This will reduce excessive renders when using the pureRenderMixin.

The same should be possible for for merge, but is more complicated so is not
attempted here.

Addresses #1923

For $set and $apply it is cheap and easy to check whether the new value will
be identical (===) to the old value and create a new object only when this is not
the case. This will reduce excessive renders when using the pureRenderMixin.

The same should be possible for for merge, but is more complicated so is not
attempted here.
@sophiebits
Copy link
Collaborator

No, we'll land it on master if we take it (and it will be after 0.14, whose release is imminent).

@sophiebits sophiebits closed this Oct 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants