Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PERF beta] @each should remain a stable node for chains. #11984

Merged
merged 1 commit into from
Aug 6, 2015
Merged

Conversation

krisselden
Copy link
Contributor

@each was designed for chaining, the special cased eager behavior + it invalidating for array changes meant that the EachProxy and chains were rebuilt every array change, instead of the leaves just changing.

@stefanpenner
Copy link
Member

Do we need to deprecate in 1.13?

@rwjblue
Copy link
Member

rwjblue commented Aug 5, 2015

@stefanpenner - Yes, I was thinking similarly...

@rwjblue
Copy link
Member

rwjblue commented Aug 6, 2015

After chatting with @krisselden about this, I think there were a few later tweaks to #11990 that still need to be made here.

@krisselden - Please let us know when those are ready (no rush at all).

@krisselden
Copy link
Contributor Author

@rwjblue all the further cleanup that was in #11990 has been made in this PR.

`@each` was designed for chaining, the special cased eager behavior + it invalidating for array changes meant that the EachProxy and chains were rebuilt every array change, instead of the leaves just changing.
Conflicts:
	packages/ember-runtime/lib/system/each_proxy.js
	packages/ember-runtime/tests/mixins/array_test.js
rwjblue added a commit that referenced this pull request Aug 6, 2015
[PERF beta] `@each` should remain a stable node for chains.
@rwjblue rwjblue merged commit 62e3259 into master Aug 6, 2015
@rwjblue rwjblue deleted the fix-each branch August 6, 2015 20:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants