perf(animations): Remove generic objects in favor of Maps#44482
perf(animations): Remove generic objects in favor of Maps#44482jessicajaniuk wants to merge 1 commit intoangular:masterfrom
Conversation
e233f8f to
be7e805
Compare
f2c3799 to
24cacd0
Compare
74bec63 to
84cc81b
Compare
0e15016 to
9698f71
Compare
atscott
left a comment
There was a problem hiding this comment.
reviewed-for: public-api
6437971 to
54e52f8
Compare
8954cb4 to
24b7039
Compare
dylhunn
left a comment
There was a problem hiding this comment.
reviewed-for: public-api
There was a problem hiding this comment.
@jessicajaniuk In PR #44729 I am adding a delete tuple[prop] here, after the PR has been merged please remember to update it to tuple.delete(prop) whenever you can 🙂
Original discussion: https://github.com/angular/angular/pull/44729/files#r787206809
dylhunn
left a comment
There was a problem hiding this comment.
reviewed-for: fw-core, fw-testing, public-api
|
TGP is green |
AndrewKushnir
left a comment
There was a problem hiding this comment.
Reviewed-for: public-api
There was a problem hiding this comment.
nit: I like the StyleData as a symbol name a bit more. The Map part leaks the implementation detail into the name (for ex. we'd need to change the name if we later decide to use an array).
This is a very minor thing, not a blocker for this PR :)
There was a problem hiding this comment.
I actually agree, but we still use the old symbol. We'd need a new name. I'll think on it for a potential refactor after this PR.
We were using a number of generic objects as if they were maps and relying on delete to remove properties. In order to improve performance, these have been switched to native maps.
|
This PR was merged into the repository by commit 7a81481. |
|
@jessicajaniuk OOC do you have performance numbers before/after? |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
We were using a number of generic objects as if they were maps and relying on delete to remove
properties.
Issue Number: N/A
What is the new behavior?
In order to improve performance, these generic objects have been switched to native maps.
Does this PR introduce a breaking change?