Optimize Data.Array.Mutable.Unlifted.Linear.map#334
Merged
Conversation
aspiwack
approved these changes
Jun 28, 2021
Co-authored-by: Arnaud Spiwack <arnaud.spiwack@tweag.io>
e4d62f8 to
afa7d29
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR implements
mapfunction in the PR in a simpler way, directly on top ofArray#'s. It's as fast as themapfunction onData.Vectornow.In order to be able to measure the results, I also split up a benchmark using
mapandtoListto two benchmarks each testing a single function.Without
{-# NOINLINE map #-}our benchmarks improve a bit. However, I'm keeping it as per the discussion around #187 (comment).Related: #328