Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Optimise state transfer from probe() to apply() #23

Open
DavePearce opened this issue Oct 30, 2015 · 0 comments
Open

Optimise state transfer from probe() to apply() #23

DavePearce opened this issue Oct 30, 2015 · 0 comments
Labels
Optimisation Useful

Comments

@DavePearce
Copy link
Member

Currently, I don't believe much thought has been given to the amount of state being passed from probe() to apply(). From a cursory glance, it looks like a lot of unnecessary stuff maybe being passed through.
@DavePearce DavePearce changed the title Optimise state transfer from <code>probe()</code> to <code>apply()</code> Optimise state transfer from probe() to apply() Nov 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Optimisation Useful
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DavePearce