Jonathan Grynspan

[WIP] Add DOS-/Windows-style command line parsing

3

**⚠️ Not ready for merging yet!** ### Description This change introduces support for DOS-/Windows-style command line parsing. Historically, DOS and Windows have used a different set of rules for parsing...

Please add a `TriviaPiece.commentValue` property

19

### Description There are four kinds of comment tracked by `TriviaPiece`. It'd be a nice convenience to be able to extract the string values of those comments. May I suggest...

Backticks on identifiers should be separate tokens

16

### Description If I have an expression like so: ```swift let x = y.`z`() ``` Then the syntax node representing `z` contains the surrounding backticks. I then need to strip...

"`EffectfulExprSyntax`" protocol covering `TryExprSyntax` and `AwaitExprSyntax`

1

### Description It'd be very helpful to have a protocol that covers all effectful expressions (currently `TryExprSyntax` and `AwaitExprSyntax`.) swift-testing needs to walk syntax trees and diagnose when either of...

Modify `assertMacroExpansion()` so that it only conditionally calls `XCTFail()`.

1

This PR changes the signature of `assertMacroExpansion()` such that an alternative failure handler can be passed for use when e.g. swift-testing is being used. Right now, the function calls `XCTAssertEqual()`,...

Needed: variant of `assertMacroExpansion()` that does not use XCTest

1

### Description Test targets that use swift-testing instead of XCTest need some way to work with this function; let's add a throwing equivalent that can be used without any dependency...

makeUniqueName() produces tokens that cannot be used as closure arguments

13

### Description If I attempt to label closure arguments during macro expansion: ```swift let arg0 = context.makeUniqueName("") return """ { \(arg0) in ... } """ ``` The compiler complains: >...

Copying a node breaks its source location

2

### Description When building a macro, it is commonplace to take a syntax node from the original tree and copy it into a new position, e.g. by constructing a `TupleExprElementSyntax`...

Enhancement request: interface to get the wasi-libc version at runtime

22

I work on a Swift testing library, swift-testing (https://github.com/apple/swift-testing). I'm looking at adding Wasm/WASI support using the SwiftWasm toolchain (https://www.swiftwasm.org/). One of the things we do when starting a test...

Remove string literal tags.

1

As discussed [in the forums](https://forums.swift.org/t/removal-of-string-literal-tag-definitions/71667), we are removing string literal tags. This PR removes the interfaces for them. It preserves `Tag.Kind` because that may prove to be a useful abstraction...