-
Notifications
You must be signed in to change notification settings - Fork 557
-
Notifications
You must be signed in to change notification settings - Fork 557
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
[Proposal] Memo in another manner #100
Comments
Pros:
|
|
I didn't imagine that this extra runtime property check can make the whole app slower. In this case, please close my proposal. However, in the case to use memo in all components, this extra function call is getting the app slower, isn't it? |
@aralroca Yes, that's why it's recommended just in a few places to fix performance holes. |
A |
Thanks @dantman for clarification |
Problem
memo approach is enough understandable. However is not 100% elegant solution... Especially if you have more "wrappers" like connect, withRouter, or other HOC:
Proposal
I will propose to do it following components configurations as displayName, propTypes, defaultProps...
Something like:
or
The text was updated successfully, but these errors were encountered: