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
Unlike Ruby, which just uses a prefix 0 to denote octal literals, Crystal uses 0o (which I really like). However, this difference is not handled in the current syntax highlighter, meaning octal literals have no scope applied to them, and thus can't be highlighted.
To match other numeric literals, octal literals should get the scope constant.numeric.crystal.
The text was updated successfully, but these errors were encountered:
Support for octal numbers is already part of the syntax. I'm not sure why this particular case wasn't highlighting before, but I went back to it and it is now. This issue can probably be closed unless someone else has a way of reproducing it?
Unlike Ruby, which just uses a prefix
0
to denote octal literals, Crystal uses0o
(which I really like). However, this difference is not handled in the current syntax highlighter, meaning octal literals have no scope applied to them, and thus can't be highlighted.To match other numeric literals, octal literals should get the scope
constant.numeric.crystal
.The text was updated successfully, but these errors were encountered: