Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nimble 14: Fix broken tests in swift 6 #1169

Closed
wants to merge 30 commits into from

Conversation

younata
Copy link
Member

@younata younata commented Oct 14, 2024

The PR should summarize what was changed and why. Here are some questions to
help you if you're not sure:

  • What behavior was changed?
  • What code was refactored / updated to support this change?
  • What issues are related to this PR? Or why was this change introduced?

Checklist - While not every PR needs it, new features should consider this list:

  • Does this have tests?
  • Does this have documentation?
  • Does this break the public API (Requires major version bump)?
  • Is this a new feature (Requires minor version bump)?

Make Predicate's closure Sendable, and make Predicate Sendable when the returning value is Sendable
* Update Require DSL to largely be Sendable

* Fix now-broken tests
* Make FailureMessage sendable.

* Make MatcherResult conform to Sendable
Still more to do here. Will likely to require further refactoring
There are 2 subclasses which are also sendable/safe to use. And no one else can make subclasses outside of Nimble, so this is tolerable
@younata younata mentioned this pull request Oct 14, 2024
1 task
@younata younata force-pushed the nimble-13-failing-tests branch from 259705b to efd7a78 Compare October 14, 2024 05:51
@younata younata force-pushed the nimble-13-failing-tests branch from 2ff6980 to d28c8ed Compare October 15, 2024 03:47
@gremlinflat
Copy link

any update for this? i've been experiencing this error on xcode 16 (swift 6)

@younata younata closed this Dec 20, 2024
@younata younata deleted the nimble-13-failing-tests branch December 20, 2024 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants