Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Names for Rules Variables are difficult to understand in context #9

Open
aSemy opened this issue Apr 13, 2024 · 0 comments
Open

Names for Rules Variables are difficult to understand in context #9

aSemy opened this issue Apr 13, 2024 · 0 comments

Comments

@aSemy
Copy link

aSemy commented Apr 13, 2024

The spec describes 4 rule variables, n, m, c, and t.

I find a terse, single letter, variable in the spec difficult for two reasons:

  1. When looking at the rules, it is difficult to remember what each letter means. If the variables were named with a brief summary of the actual value, it would be easier to remember the actual meaning.
  2. The short names make searching for usages impossible. If the names were distinct, then it would be possible to quickly find usages and the definition.

I would find the spec easier to understand if the names were more descriptive. For example:

  • ncurrentIndent
  • madditionalIndent
  • ccurrentContext
  • twhitespaceTrim
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant