You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
This is basically the same as #37 except for triple-quoted raw strings.
#foo above should be highlighted as a comment. Instead, it and everything else that comes later in the file will get highlighted as if it were a regex. The grammar doesn't see that the raw string got closed at the closing triple-quote, so is happily consuming everything into the string.
The rules for triple-quoted strings use begin/end to make them work over multiple lines. We could fix the single-line case by adding near-duplicate match rules ("match": "r\"\"\"(.*)\"\"\" e.g.). But the multi-line case would still be broken:
I'm not sure how to fix the multi-line case given the way grammars currently work.
This is basically the same as #37 except for triple-quoted raw strings.
#fooabove should be highlighted as a comment. Instead, it and everything else that comes later in the file will get highlighted as if it were a regex. The grammar doesn't see that the raw string got closed at the closing triple-quote, so is happily consuming everything into the string.The rules for triple-quoted strings use
begin/endto make them work over multiple lines. We could fix the single-line case by adding near-duplicatematchrules ("match": "r\"\"\"(.*)\"\"\"e.g.). But the multi-line case would still be broken:I'm not sure how to fix the multi-line case given the way grammars currently work.