-
Notifications
You must be signed in to change notification settings - Fork 104
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
Spell fixes by codespell
#860
Comments
Vaguely related, perhaps we should have an identifier policy. An identifier:
Checking for identifiers in C++ is easy (the hard part is figuring out what they mean), so we could possibly just feed them to some password policy checker. |
I take it that @klenze 's comment fall in the "Surely You're Joking ?" category. The original suggestion is intended as a small one-time action unrelated to any CI or policy. |
Yes, I was. No harm in anyone checking and fixing misspellings, I guess. Not in my top ten complaints about the code base, but that may be because I am the one doing the misspelling. |
For someone wanting some fun with
git diff --word-diff
and other such games, the nice toolcodespell
can be used to clean up some misspellings in the sources.git diff --word-diff
is needed to check the results, since not all changes are good. But experience from other places is that it is quite rewarding. The options-L
and-w
, as well as-i 2
ofcodespell
are useful to look up to.One does not need to deal with the entire repository at once.
The text was updated successfully, but these errors were encountered: