Route using map rather than fold to prevent state from parameters affecting the outer state #3310
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Bug Fix
What does this PR do / why is it needed ?
Currently, routing does a fold of the parameters of a function, and takes the output of that fold as the state to also route the outer function.
This has two side effect:
One visible outcome is when expressions have multiple
from()
, where these are not properly respected, leading to incorrect routing.This PR also start treating let as a specialize function to ensure the platform generates the proper allocations nodes.
List of features this would enable: