Add reusing misspelling and variants

[korverdev]

This contains the same changes as #3443. Creating a second PR to get around the incorrect code coverage check the prior PR was failing.

[DimitriPapadopoulos]

View this Pull Request on Codecov

87.35% (-1.23%) compared to 383a32c

Something's very wrong, 383a32c is an old commit from last January. Why does Codecov compare to 383a32c?

[DimitriPapadopoulos]

All I can think of is that intermediate coverage reports have somehow been lost.

[DimitriPapadopoulos]

@larsoner Based on "How to prevent codecov from using a commit older than the base of the PR to do comparison?" I suspect there is no way to convince Codecov to compare with the last commit instead of 383a32c, probably because intermediate coverage data has been lost somehow. If so, the only solution is to "change the status checks to be informational until the repository stabilizes".

[larsoner]

Let's see if it stabilizes soon... in theory it should only take one commit, so maybe after a couple Codecov will figure things out. If not then yes we can change to informative

[corneliusroemer]

re-using isn't necessarily a typo. Hyphen is used in almost 10% of cases, so this will cause very very many changes.

Is there a separate dictionary for opinionated changes? This shouldn't be in the main dict.

https://books.google.com/ngrams/graph?content=reuse%2Cre-use&year_start=1800&year_end=2022&case_insensitive=true&corpus=en&smoothing=3

See #3521

[DimitriPapadopoulos]

Curated dictionaries and SCOWLS (And Friends) only have reuse. The grammar rule is Use the hyphen with the prefix re only when re means again AND omitting the hyphen would cause confusion with another word.