Add Swift Testing Compatibility#310
Open
toastersocks wants to merge 2 commits intotypelift:masterfrom
Open
Conversation
- Make package compatible with Swift 6
|
Any ETA when this is going to be reviewed/merged? |
Author
|
@popovych-y I don't think this repo is actively maintained anymore. I think the maintainers are working at Apple now so it's unlikely this will ever be merged. My fork with this fix plus some additional fixes is here: https://github.com/toastersocks/SwiftCheck |
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
2 participants
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.
What's in this pull request?
Adds compatibility with the Swift Testing (swift-testing) framework while maintaining the existing compatibility with XCTest.
Why merge this pull request?
This would allow SwiftCheck to be used with Swift Testing.
What's worth discussing about this pull request?
I don't think so, but happy to discuss.
What downsides are there to merging this pull request?
None that I know of.