Simplify deepseq workaround #162
Merged
Conversation
This file contains 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
Calculating the length of a lazy `ByteString` forces it deeply (each chunk has to be examined and their lengths summed). Thus we can use `BSL.length` instead of copying the `deepseq` definition. Really, we *should* use `deepseq` when `bytestring` is new enough, in case some future change invalidates this workaround.
mightybyte
added a commit
that referenced
this pull request
Nov 29, 2015
Simplify deepseq workaround
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Calculating the length of a lazy
ByteStringforces it deeply (each chunk has to be examined and their lengths summed). Thus we can useBSL.lengthinstead of copying thedeepseqdefinition.Really, we should use
deepseqwhenbytestringis new enough, in case some future change invalidates this workaround.