Xiaodi Wu
Xiaodi Wu
The link above describes a real-world situation in which the current behavior actively misled a user to believe that they were using an existential type when they were not. Given...
See #20
```swift let digits = CharacterSet.decimalDigits print(digits.intersection(digits.inverted).isEmpty) // false print(digits.intersection(digits.inverted) == digits.inverted.intersection(digits)) // false ``` Oops...
Just spitballing—could there be some way to alter the macro expansion itself so as to be insensitive to any `try` or `await` that precedes it? For example, would wrapping the...
> No, that wouldn't work unfortunately. All that does is add another spot where we might need `try` or `await` I wasn't under the impression that the specific text I...
Yeah, I see your point. Going in the other direction, how confident can we be that `await` and `try` are the only or even most of the cases now that...
apple/swift-syntax#2689 @swift-ci build toolchain
apple/swift-syntax#2689 @swift-ci build toolchain
@mateusrodriguesxyz Would it be wise to add tests that exercise the code paths where you've made changes in response to @ahoppen?
https://github.com/swiftlang/swift-syntax/pull/2689 @swift-ci build toolchain