Jonathan Grynspan
Jonathan Grynspan
`withKnownIssue()` also takes an (optional) second closure for examining the issue and matching it in the same fashion. :)
@swift-ci please test
Windows failure is a known compiler issue.
I don't think that name would be particularly idiomatic Swift. ☹️ We already have `withKnownIssue()` (and the name, we think, is appropriate for its existing/intended uses) and I'm bikeshedding ways...
Oh, it's the same as function invocation syntax here (just drop the pound character.) The first trailing closure is the body of code to which the expectation is applied; the...
Unfortunately that isn't valid Swift syntax. Only the second (and onward) trailing closure gets a label. The first trailing closure is unlabelled.
Thanks for the suggestions. The team will take a look at the API and see if there are areas where we can improve it.
Tracked internally by rdar://137211023.
This may be of interest to you, Dave: #780
i.e. we could extrapolate from there to: ```swift let issue = #expect(records: Issue.self) { ... } guard case let .expectationFailed(expectation) = issue?.kind else { // TBD: failure mode--really, `case let`...