Don't capture arguments to #expect(exitsWith:) during macro expansion.#912
Merged
Conversation
Other than the body closure, the arguments to `#expect(exitsWith:)` are not
guaranteed to be literals or otherwise context-free, but we capture them during
macro expansion. This can result in obscure errors if the developer writes an
exit test with an argument that is computed:
```swift
let foo = ...
await #expect(exitsWith: self.exitCondition(for: foo)) {
// 🛑 error: closure captures 'foo' before it is declared
// 🛑 error: enum declaration cannot close over value 'self' defined in outer scope
// (and other possible errors)
...
}
```
This PR removes the macro's compile-time dependency on its `exitCondition` and
`sourceLocation` arguments and introduces an `ID` type to identify exit tests
(instead of using their source locations as unique IDs.) The `ID` type is meant
to be a UUID, but for the moment I've just strung together two 64-bit integers
instead to avoid a dependency on Foundation or platform API.
Contributor
Author
|
@swift-ci test |
Contributor
Author
|
@swift-ci test |
stmontgomery
approved these changes
Jan 15, 2025
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.
Other than the body closure, the arguments to
#expect(exitsWith:)are not guaranteed to be literals or otherwise context-free, but we capture them during macro expansion. This can result in obscure errors if the developer writes an exit test with an argument that is computed:This PR removes the macro's compile-time dependency on its
exitConditionandsourceLocationarguments and introduces anIDtype to identify exit tests (instead of using their source locations as unique IDs.) TheIDtype is meant to be a UUID, but for the moment I've just strung together two 64-bit integers instead to avoid a dependency on Foundation or platform API.Checklist: