Keith Hall
Keith Hall
I've logged a new issue at https://github.com/trishume/syntect/issues/104 which details why the ASP syntax tests are still failing, and an additional bug which doesn't show up in the official ST default...
I think the reason why the LaTeX syntax has a failure in `syntect` is due to how ST and `syntect` optimize the matching - ST seems to check "does this...
My knowledge of how Sublime works internally is of course not really knowledge at all but educated guesswork, based on my experiences and some posts made by sublimehq - that...
Thanks Jon, useful bit of info to know :+1: that should resolve the differences in how `syntect` parses LaTeX compared to ST :fireworks:
It's a big feature, the current line by line api isn't suitable, because parsing the next line could affect the tokens for the previous line if there was a branch...
Pretty sure ST has no problem with `\G` - the old Markdown syntax used to be littered with them. But yes, any `tmLanguage` features introduced in the last few years...
No, Typescript support is dependant on https://github.com/trishume/syntect/issues/271 and https://github.com/trishume/syntect/issues/323
I had a go at this, with keeping the "read and process one line at a time" behavior (as opposed to Sublime's "read the whole syntax test file into memory...
> I'm not entirely sure how the architecture works, but are there any other things I can optimize by caching? Regex compilation? (I assume the packdump already has them compiled...
see also https://github.com/chyh1990/yaml-rust/issues/118