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
We currently use a convention where we quote token names and leave predefined special keys (e.g. inside, greedy etc) unquoted, but that's a bit obscure, and it means that any code that handles grammars needs to maintain a list of special keys to figure out what the actual tokens are. Using a naming convention makes that very clear and gives us several benefits:
Code that handles grammars can figure out what is a token name without hardcoding all special keys
Token names and special keys can co-exist in the same object literal
Much more obvious what is what
The text was updated successfully, but these errors were encountered:
We currently use a convention where we quote token names and leave predefined special keys (e.g.
inside
,greedy
etc) unquoted, but that's a bit obscure, and it means that any code that handles grammars needs to maintain a list of special keys to figure out what the actual tokens are. Using a naming convention makes that very clear and gives us several benefits:The text was updated successfully, but these errors were encountered: