Require qcheck-core.0.23 #491
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
|
CI summary for 2684c1b: all 31 workflows pass. CI summary for merge to |
Merged
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.
This PR bumps the qcheck-core lower bound to 0.23.
This freshly-released version means the
Util.Pp.pp_fun_output will contain properly escaped and quoted chars and strings, and thus more comprehensible - see, e.g., the expect test diff in ef6c006.As an added benefit, the new lower-bound means the Lin and STM show functions can be simplified,
as they no longer need to work around QCheck.Print's lack of quoting and escaping.