Merge pull request #840 from DougGregor/keypath-integer-literal-component

Fix parsing of key paths that involve `.<integer literal>`.

Author: DougGregor

Sources/SwiftParser/Expressions.swift

@@ -553,10 +553,12 @@ extension Parser {
 
       // Check for a .foo suffix.
       if self.at(any: [.period, .prefixPeriod]) {
-        // A key path is special, because it allows .[, unlike anywhere else. The
-        // period itself should be left in the token stream. (.? and .! end up
-        // being operators, and so aren't handled here.)
-        if periodHasKeyPathBehavior && self.peek().tokenKind == .leftSquareBracket {
+        // A key path is special, because it allows .[ and .<N>, unlike
+        // anywhere else. The period itself should be left in the token stream.
+        // (.? and .! end up being operators, and so aren't handled here.)
+        if periodHasKeyPathBehavior &&
+            (self.peek().tokenKind == .leftSquareBracket ||
+             self.peek().tokenKind == .integerLiteral) {
           break
         }
 

Tests/SwiftParserTest/Expressions.swift

@@ -111,6 +111,12 @@ final class ExpressionTests: XCTestCase {
       #"""
       _ = \Lens<[Int]>.[0]
       """#)
+
+    AssertParse(
+      #"""
+      \(UnsafeRawPointer?, String).1
+      """#
+    )
   }
 
   func testBasicLiterals() {