Set infixr of 'deepseq' to be consistent with 'seq' #56
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
|
So, morally this seems like the right thing to do, but I want to make sure there are no unintended consequences. Can't think of any off the top of my head. CC @haskell/core-libraries-committee |
|
yeah, this is pretty unoffensive to me. |
|
@martijnbastiaan this needs a changelog entry before merging |
|
@chessai Sorry for the delay, done! |
Without this patch the following code:
a `deepseq` a : as
gets parsed as
(a `deepseq` a) : as
instead of
a `deepseq` (a : as)
Note that infix use of 'seq' already behaves like this.
bgamari
added a commit
that referenced
this pull request
Apr 16, 2021
This is a breaking change and won't be in deepseq-1.4. This reverts commit f87570c.
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.
Without this patch the following code:
gets parsed as
instead of
Note that
seqalready behaves like this.We had similar problems over at clash-lang/clash-compiler for our Clash-specific version of deepseq causing pretty bad memory leaks.