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
From my understanding the separation for what gets compressed and what doesn't for SyntaxReferences are whether the values are expected to be used when trying to match on the syntax vs actually highlighting using the syntax. By that logic I believe that variables should also be compressed until used (lingering question: should this be included within LazyContexts or kept separate?)
The main motivation being that some syntax definitions have very large variables that wind up bloating the serialized size of SyntaxSets. For instance C.sublime-syntax has a window_types variable that's over a KiB (and bat's Julia sublime syntax has a variable with a value that's over 8 KiBs by itself)
The text was updated successfully, but these errors were encountered:
From my understanding the separation for what gets compressed and what doesn't for
SyntaxReference
s are whether the values are expected to be used when trying to match on the syntax vs actually highlighting using the syntax. By that logic I believe thatvariables
should also be compressed until used (lingering question: should this be included withinLazyContexts
or kept separate?)The main motivation being that some syntax definitions have very large variables that wind up bloating the serialized size of
SyntaxSet
s. For instanceC.sublime-syntax
has awindow_types
variable that's over a KiB (andbat
's Julia sublime syntax has a variable with a value that's over 8 KiBs by itself)The text was updated successfully, but these errors were encountered: