-
Notifications
You must be signed in to change notification settings - Fork 150
Exit tests should be able to capture values #1157
Copy link
Copy link
Labels
api-proposalAPI proposal PRs (documentation only)API proposal PRs (documentation only)enhancementNew feature or requestNew feature or requestexit-tests☠️ Work related to exit tests☠️ Work related to exit testsmacros🔭 Related to Swift macros such as @Test or #expect🔭 Related to Swift macros such as @Test or #expectparameterized-testingRelated to parameterized testing functionalityRelated to parameterized testing functionalitypublic-apiAffects public APIAffects public APItriagedThis issue has undergone initial triageThis issue has undergone initial triage
Milestone
Metadata
Metadata
Assignees
Labels
api-proposalAPI proposal PRs (documentation only)API proposal PRs (documentation only)enhancementNew feature or requestNew feature or requestexit-tests☠️ Work related to exit tests☠️ Work related to exit testsmacros🔭 Related to Swift macros such as @Test or #expect🔭 Related to Swift macros such as @Test or #expectparameterized-testingRelated to parameterized testing functionalityRelated to parameterized testing functionalitypublic-apiAffects public APIAffects public APItriagedThis issue has undergone initial triageThis issue has undergone initial triage
Type
Fields
Give feedbackNo fields configured for Feature.
Exit tests should be able to capture values. We can constrain this to values conforming to
SendableandCodable.An implementation exists on the main branch guarded by the package trait
ExperimentalExitTestValueCaptureand@_spi(Experimental).