4 Commits

Author	SHA1	Message	Date
Alex Hoppen	749a13a6fe	[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.	2018-07-30 09:26:18 -07:00
Alex Hoppen	6bc1b5a389	[libSyntax] Add test variants for building the syntax map via libSyntax	2018-07-13 17:57:00 -07:00
John Fairhurst	677491fc9b	[SourceKit] Add syntaxtype for #error/#warning (#14742)	2018-02-21 14:48:18 -08:00
David Farler	6c726620c0	SourceKit: Clean up syntax map switch ... When creating the token map for highlighting, there is some glitchy behavior that needed to be cleaned up: - New image literal syntax wasn't getting highlighted as an object literal keyword. - Other #-prefixed keywords had no data - #line would appear as a build config ("brown") at the start of a line - #available showed up as a build config. However, this should be a keyword because it is a runtime check, not a build configuration. Add some test cases for these. Fixes: rdar://problem/26451674	2016-05-24 17:34:22 -07:00