[WIP] Ensure correct shaping for isDestroy[ing|ed] on CoreObject.#13782
[WIP] Ensure correct shaping for isDestroy[ing|ed] on CoreObject.#13782rwjblue wants to merge 1 commit intoemberjs:masterfrom
isDestroy[ing|ed] on CoreObject.#13782Conversation
85a5e91 to
38eaf84
Compare
Shaping the prototype is not enough, we should ensure the instance properties are set in the constructor.
38eaf84 to
f85dca2
Compare
|
@rwjblue is this something we should be benchmarking to show improvement? Or are you otherwise just waiting on review from a perf team member (I expect @krisselden or @stefanpenner )? |
|
Yeah, this is still a bit WIP (I'll update it as such). |
isDestroy[ing|ed] on CoreObject.isDestroy[ing|ed] on CoreObject.
This is most likely to small a change to notice much.
|
|
☔ The latest upstream changes (presumably #14215) made this pull request unmergeable. Please resolve the merge conflicts. |
|
@stefanpenner the states should be moved to meta, and we should have accessors on the prototype that defer to meta for backwards compatibility. I agree that this PR is a step backwards and that it is dubious to test non enumerability since they are enumerable once set currently. |
yes |
|
Completely replaced by #14359 |
Shaping the prototype is not enough, we should ensure the instance properties are set in the constructor.