7 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
Nathan Hawes	f64a19bbbe	[syntax-coloring] Relax the requirement that the reported affected range extends to line boundaries ... The editor is now assumed to handle affected ranges that don't fall on line boundaries.	2017-09-14 21:34:22 -07:00
Nathan Hawes	77d502cb39	[syntax-coloring] Fix incorrectly reporting a no-op when a token is removed	2017-09-14 21:34:21 -07:00
Nathan Hawes	90cc29bb2c	[syntax-coloring] Highlight unterminated regular and multi-line strings as strings ... Also add tests for syntax map deltas when editing multi-line strings	2017-09-14 21:34:21 -07:00
Nathan Hawes	e5426ecfa5	Revert "[SyntaxColor] Improve highligting of multiline strings" ... This reverts commit 86d0fc37bc. This was causing a performance regression. Resolves rdar://problem/32434045	2017-05-26 16:46:03 -07:00
Nathan Hawes	56fb4a5d9f	[SyntaxColor] Improve highligting of multiline strings ... Multiline strings (and multiline tokens in general) were not well supported by the existing highlighting logic. Edits on one line can make tokens appear/disappear on previous and later lines, which broke assumptions in the existing logic, and left odd ranges of source unhighlighted or out of date. This patch accounts for these changes, and also changes unterminated multiline (and regular strings) to still be highlighted as strings, so the rest of the file doesn't look like plain text. Resolves rdar://problem/32148117.	2017-05-22 16:53:32 -07:00