Use QuickCheck features in Seq property tests#1197
Merged
meooow25 merged 1 commit intohaskell:masterfrom Apr 19, 2026
Merged
Conversation
meooow25
force-pushed
the
seq-props
branch
2 times, most recently
from
ba81143 to
dcf2da3
Compare
meooow25
changed the title
Use .&&. and === wherever suitable. This leads to better failure messages compared to having a Bool. Also separate the validity checks from the equality checks for simplicity. Change some tests to use arbitrary functions where it seems suitable.
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
1 participant
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.
Use .&&. and === wherever suitable. This leads to better failure messages compared to having a Bool.
Also separate the validity checks from the equality checks for simplicity.
Change some tests to use arbitrary functions where it seems suitable.
Closes #263