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

[ST-NNNN] Add ConditionTrait.evaluate() #2740

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

Uncommon
Copy link

Proposal document moved from swiftlang/swift-testing#909

@stmontgomery stmontgomery self-requested a review March 15, 2025 19:53
@stmontgomery stmontgomery added the swift-testing Proposal relates to Swift Testing label Mar 15, 2025
@stmontgomery stmontgomery added the workgroup: needs development This proposal needs to be developed further before it can be reviewed label Mar 17, 2025
@stmontgomery stmontgomery self-assigned this Mar 19, 2025
@grynspan grynspan changed the title Add ConditionTrait.evaluate() [ST-NNNN] Add ConditionTrait.evaluate() Mar 20, 2025
stmontgomery added a commit to swiftlang/swift-testing that referenced this pull request Mar 25, 2025
…1036)

This removes a mechanism in the implementation of `ConditionTrait` for a
condition closure to provide an "override" comment.

### Motivation:

While reviewing a draft evolution proposal for `ConditionTrait`
(swiftlang/swift-evolution#2740) I realized that
we don't use this "comment override" mechanism anywhere in the testing
library. I believe we did back when it was first added, but it's no
longer used.

Removing this would allow the public API being proposed above to be
simplified: the `evaluate()` method could return `Bool` instead of a
tuple.

### Checklist:

- [x] Code and documentation should follow the style of the [Style
Guide](https://github.com/apple/swift-testing/blob/main/Documentation/StyleGuide.md).
- [x] If public symbols are renamed or modified, DocC references should
be updated.
@stmontgomery stmontgomery added workgroup: ready This proposal seems to be ready for evolution review and removed workgroup: needs development This proposal needs to be developed further before it can be reviewed labels Mar 28, 2025
@stmontgomery
Copy link
Contributor

Thank you @Uncommon. The Testing Workgroup met on 4/7/25 and agreed to begin a review for this proposal. I will be acting as the review manager and will start that process soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
swift-testing Proposal relates to Swift Testing workgroup: ready This proposal seems to be ready for evolution review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants