Reduce memory usage of benchmarks and of merge sort #11
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.
Summary with benchmark results
Benchmarking merge sort with a vector size of 250,000,000, timing results are unaffected by these commits. However, the benchmarks use:
about 9.32 GiB before these commits
about 7.45 GiB after the first commit
about 5.59 GiB after both commits
Compiling and testing
I'm unsure of whether or not the
BoundsChecks,UnsafeChecks, andInternalChecksflags actually do anything, as I didn't use them withcabal install vector. At any rate, all tests passed in all three cases above.