Jonathan Grynspan
Jonathan Grynspan
Output to `stderr` is currently unstructured, because tests can and do write to it too, so reordering the output from `ConsoleOutputRecorder` would be insufficient (you'd see the swift-testing output in...
Tracked internally (more or less) as rdar://103374320.
We're starting to plan out what we want to do for the next major Swift release. This is on our spreadsheet, although I don't know if we've assigned any particular...
Draft for now because we may end up needing to implement the relevant logic in a single location in SwiftPM so that the message reflects the _overall_ output, not per-library...
No longer required due to #536 and https://github.com/swiftlang/swift-package-manager/pull/7777.
> 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 problem is ultimately that we can only see the syntax nodes inside the macro. Unconditionally adding a try or await ahead of the expression would change the semantics of...
Mutating member function calls on value types also don't compile correctly and they are syntactically identical to non-mutating ones. There is no readily available solution, but those are relatively rare...
@swift-ci please test
FWIW rather than ` #expect(Bool(false), ...)`, write `Issue.record(...)` :)