Jonathan Grynspan
Jonathan Grynspan
This is expected and is a constraint of macros in Swift. The presence of the await keyword signals to the compiler that some subexpression of the expectation is asynchronous, but...
The same issue exists for a `try` expression. Imagine we add support for an `AwaitExprSyntax` path. What would the implementation look like? It would need to preserve `await` semantics on...
Now, it may be possible to simplify that expansion a bit given that the outermost call to `#expect()` would need an `await` keyword applied to it, but the effect keywords...
The issue can be avoided by extracting the async subexpression out into a separate expression: ```swift let y = await foo() #expect(x == y) ``` So I'd steer developers toward...
Reopening. Now that we have `#isolation`, it may be possible to avoid the unnecessary hops.
Blocked by https://github.com/swiftlang/swift/issues/76930.
Tracked internally as rdar://135437448.
Tracked by Apple as rdar://152019216.
Custom operator precedence is not available during macro expansion, so the syntax tree we see is malformed.