306712a3

By: Tom Sydney Kerckhove <syd@cs-syd.eu>

Say what the prefix rule leaves alone, and pin it

Three names the rule says nothing about, where only the operator one was
written down: an infix constructor, a field opening with an underscore, and
every name an instance of a data family introduces. The first two fall out of
reading a prefix off a name that does not open with a letter, and the third
out of reading type declarations alone. A resource holds all three, so each
is a decision rather than something the code happened to do.

Also a sentence the constructor rename walked into: a test's failure message
read "ExplanationGiven a rule this build does not have", which is a
constructor where a verb belongs.
e2e-added-rule-is-rune2e-artifacts-are-reade2e-choices-are-found-beside-the-repositorye2e-cleane2e-dirty-package-is-judged-failinge2e-dirty-project-is-judged-failinge2e-dirty-report-is-readablee2e-disabled-rule-is-not-rune2e-incomplete-artifacts-are-a-failuree2e-judging-nothing-failse2e-named-packages-are-every-packagee2e-no-packages-is-judged-failinge2e-no-store-paths-in-findingse2e-paths-are-repository-relativee2e-withheld-facts-faile2e-wrong-source-mapping-is-a-complainthlint-checkhopinionpre-commitreleaseshellweeder-checkconfiguredevShelldefaultx86_64-linux