[libSyntax] Remove the C++ SyntaxClassifier

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.
This commit is contained in:
Alex Hoppen
2018-07-27 14:14:25 -07:00
parent bae048123d
commit 749a13a6fe
38 changed files with 200 additions and 1644 deletions

View File

@@ -1,6 +1,6 @@
{
key.offset: 0,
key.length: 454,
key.length: 279,
key.diagnostic_stage: source.diagnostic.stage.swift.parse,
key.syntaxmap: [
{
@@ -13,59 +13,49 @@
key.offset: 71,
key.length: 40
},
{
key.kind: source.lang.swift.syntaxtype.comment,
key.offset: 111,
key.length: 115
},
{
key.kind: source.lang.swift.syntaxtype.comment,
key.offset: 226,
key.length: 60
},
{
key.kind: source.lang.swift.syntaxtype.keyword,
key.offset: 287,
key.offset: 112,
key.length: 3
},
{
key.kind: source.lang.swift.syntaxtype.identifier,
key.offset: 291,
key.offset: 116,
key.length: 5
},
{
key.kind: source.lang.swift.syntaxtype.objectliteral,
key.offset: 299,
key.offset: 124,
key.length: 40
},
{
key.kind: source.lang.swift.syntaxtype.keyword,
key.offset: 340,
key.offset: 165,
key.length: 3
},
{
key.kind: source.lang.swift.syntaxtype.identifier,
key.offset: 344,
key.offset: 169,
key.length: 5
},
{
key.kind: source.lang.swift.syntaxtype.objectliteral,
key.offset: 352,
key.offset: 177,
key.length: 50
},
{
key.kind: source.lang.swift.syntaxtype.keyword,
key.offset: 403,
key.offset: 228,
key.length: 3
},
{
key.kind: source.lang.swift.syntaxtype.identifier,
key.offset: 407,
key.offset: 232,
key.length: 4
},
{
key.kind: source.lang.swift.syntaxtype.objectliteral,
key.offset: 414,
key.offset: 239,
key.length: 38
}
]