We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Doesn't this entirely destroy the laziness of React components?
https://github.com/salsita/redux-elm/blob/master/src/forwardTo.js#L14
I've come up with an interesting solution here:
https://github.com/ccorcos/elmish/blob/narrative/src/tutorial/7-lazy-react/index.js#L55-L63
Where I use shouldComponentUpdate to compare dispatch functions using a .equals function that remembers all the partially applied types...
.equals
The text was updated successfully, but these errors were encountered:
Yeah, forwardTo indeed returns a new reference.
forwardTo
However, I am not really fan of storing memoized function arguments in the function reference itself. I could imagine _.memoize could do the trick.
_.memoize
We have to decide how we want to handle this, because I do believe that this kind of performance optimization should be in user land.
Sorry, something went wrong.
_.memoize doesnt clean up though. you'll have a memory explosion.
No branches or pull requests
Doesn't this entirely destroy the laziness of React components?
https://github.com/salsita/redux-elm/blob/master/src/forwardTo.js#L14
I've come up with an interesting solution here:
https://github.com/ccorcos/elmish/blob/narrative/src/tutorial/7-lazy-react/index.js#L55-L63
Where I use shouldComponentUpdate to compare dispatch functions using a
.equals
function that remembers all the partially applied types...The text was updated successfully, but these errors were encountered: