You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To make serial and concurrent folds work the same way, "step" function should just change the state and not return the Done/Partial status. The status should be returned independently by the "extract" function. That way for concurrent folds/scans we can just send the inputs in "step" and then gather the results in "extract" asynchronously. With this change we should be able to implement concurrent scan combinators in a modular way, in terms of parEval.
But this may have an impact on fusion characteristics of serial folds.
The text was updated successfully, but these errors were encountered:
To make serial and concurrent folds work the same way, "step" function should just change the state and not return the Done/Partial status. The status should be returned independently by the "extract" function. That way for concurrent folds/scans we can just send the inputs in "step" and then gather the results in "extract" asynchronously. With this change we should be able to implement concurrent scan combinators in a modular way, in terms of parEval.
But this may have an impact on fusion characteristics of serial folds.
The text was updated successfully, but these errors were encountered: