[WIP - discussion] - Alternate Method of Seq.map chaining #1528
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.
@forki
Hey, this is an example of the method I suggested for Seq.map chaining in #1525. I believe it could be safer than an expression optimizer. That said, I don't think this method has a very wide range of applicable situations. And although this method makes chaining
Seq.map
a decent amount faster for 64-bit (40% when just chaining theid
function 4 times), it comes at the cost of more allocations; it also appears to do very little for 32-bit.Chained with Cast = Map int->double->int->string->double->int
Chained = Map
id
4 timesDouble = Map
id
twiceSingle = Map
id
once