-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Create FunctionMeta
to store metadata for functions.
#13800
Conversation
d1ccd14
to
1ae6d8d
Compare
☔ The latest upstream changes (presumably #14117) made this pull request unmergeable. Please resolve the merge conflicts. |
1ae6d8d
to
0092324
Compare
Just rebased this. It seems likely that we will land #13783 before landing this. If that is what we do, I'll be able to refactor things around to share the |
☔ The latest upstream changes (presumably #14267) made this pull request unmergeable. Please resolve the merge conflicts. |
0092324
to
534cfbc
Compare
This PR has been updated to account for changes in the codebase (putting the @chancancode - Can you do a run of this against current master in ember-bench so we can confirm no performance regressions? @krisselden - This is ready for another round of review... |
534cfbc
to
6bb5064
Compare
☔ The latest upstream changes (presumably #14359) made this pull request unmergeable. Please resolve the merge conflicts. |
e081a30
to
923cfd5
Compare
This allows us to stop holding state information on functions themselves (aka stop treating functions as a "bag of properties"). Once this PR lands we will still be storing these function meta objects on the function itself (in either a `WeakMap` when supported or on a `__ember_function_meta__` property when `WeakMap` is not present) just like we store normal object meta.
☔ The latest upstream changes (presumably #14649) made this pull request unmergeable. Please resolve the merge conflicts. |
replaced by #16595 |
This allows us to stop holding state information on functions themselves (aka stop treating functions as a "bag of properties").
Once this PR lands we will still be storing these function meta objects on the function itself (in either a
WeakMap
when supported or on a__ember_function_meta__
property whenWeakMap
is not present) just like we store normal object meta./cc @krisselden