mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
749a13a6fe
The recommended way forward is to use the SyntaxClassifier on the Swift side. By removing the C++ SyntaxClassifier, we can also eliminate the -force-libsyntax-based-processing option that was used to bootstrap incremental parsing and would generate the syntax map from a syntax tree.
40 lines
1.4 KiB
Swift
40 lines
1.4 KiB
Swift
// RUN: %sourcekitd-test -req=open -print-raw-response %S/Inputs/syntaxmap-partial-delete.swift == -req=edit -print-raw-response -pos=2:10 -length=2 -replace='' %S/Inputs/syntaxmap-partial-delete.swift | %sed_clean > %t.response
|
|
// RUN: %FileCheck -input-file=%t.response %s
|
|
|
|
// CHECK: {{^}}{
|
|
// CHECK-NEXT: key.offset: 0,
|
|
// CHECK-NEXT: key.length: 13,
|
|
// CHECK-NEXT: key.diagnostic_stage: source.diagnostic.stage.swift.parse,
|
|
// CHECK-NEXT: key.syntaxmap: [
|
|
// CHECK-NEXT: {
|
|
// CHECK-NEXT: key.kind: source.lang.swift.syntaxtype.keyword,
|
|
// CHECK-NEXT: key.offset: 1,
|
|
// CHECK-NEXT: key.length: 3
|
|
// CHECK-NEXT: },
|
|
// CHECK-NEXT: {
|
|
// CHECK-NEXT: key.kind: source.lang.swift.syntaxtype.identifier,
|
|
// CHECK-NEXT: key.offset: 5,
|
|
// CHECK-NEXT: key.length: 1
|
|
// CHECK-NEXT: },
|
|
// CHECK-NEXT: {
|
|
// CHECK-NEXT: key.kind: source.lang.swift.syntaxtype.number,
|
|
// CHECK-NEXT: key.offset: 9,
|
|
// CHECK-NEXT: key.length: 3
|
|
// CHECK-NEXT: }
|
|
// CHECK-NEXT: ],
|
|
|
|
|
|
// After removing 2 chars from number literal
|
|
|
|
// CHECK: {{^}}{
|
|
// CHECK-NEXT: key.offset: 9,
|
|
// CHECK-NEXT: key.length: 1,
|
|
// CHECK-NEXT: key.diagnostic_stage: source.diagnostic.stage.swift.parse,
|
|
// CHECK-NEXT: key.syntaxmap: [
|
|
// CHECK-NEXT: {
|
|
// CHECK-NEXT: key.kind: source.lang.swift.syntaxtype.number,
|
|
// CHECK-NEXT: key.offset: 9,
|
|
// CHECK-NEXT: key.length: 1
|
|
// CHECK-NEXT: }
|
|
// CHECK-NEXT: ],
|