[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

@@ -41,6 +41,8 @@ private:
llvm_unreachable("unexpected error");
}
bool syntaxMapEnabled() override { return true; }
bool handleSyntaxMap(unsigned Offset, unsigned Length, UIdent Kind) override {
return false;
}
@@ -49,6 +51,8 @@ private:
UIdent Kind, bool isSystem) override {
return false;
}
bool documentStructureEnabled() override { return false; }
bool beginDocumentSubStructure(unsigned Offset, unsigned Length,
UIdent Kind, UIdent AccessLevel,
@@ -109,8 +113,6 @@ private:
std::vector<SourceFileRange> ReuseRegions) override {
return false;
}
bool forceLibSyntaxBasedProcessing() override { return false; }
};
struct DocUpdateMutexState {