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
enumHayesCommand{/// Commands per the V.250 aka V.25TER AT standard, plus the ETSI TS 127 007/// standard.V250(v250::Command),/// Extensions to the above that we support.Extension(extension::Command),}
Both V250 and Extension should have the same scopes applied, since there is no syntactical difference between them ie. they are both variants of an enum. Neither trigger a compiler or clippy warning.
(I'm not particularly tied to V250 as a name, nor do I mind the inconsistent highlighting for this single example. I just noticed it because V250 is the first abbreviation of "V.250" I thought of that was syntactically allowed, and here we are.)
Sublime Text Version
Sublime Text 4 (Build 4142)
Rust Enhanced Version
v2.25.0
Operating system
Ubuntu 22.10, Gnome 43.0
Expected behavior
Both
V250
andExtension
should have the same scopes applied, since there is no syntactical difference between them ie. they are both variants of an enum. Neither trigger a compiler or clippy warning.(I'm not particularly tied to
V250
as a name, nor do I mind the inconsistent highlighting for this single example. I just noticed it becauseV250
is the first abbreviation of "V.250" I thought of that was syntactically allowed, and here we are.)Actual behavior
The text
V250
has the following scopes:Extension
has the following scopes:Many syntax highlighting schemes, including the default Monokai, highlight these differently:
Steps to reproduce
Code above.
The text was updated successfully, but these errors were encountered: