Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I did this:
find . -name '*.p[ml]' | xargs perltidy -b -pt=2 -mft=1 -l 88 --no-valign
Interestingly, even though (in fine Perl form)
perltidy
has a bazillion formatting options, they really want to vertically align all the=>
in a hash or=
in subsequent assignments. I discovered at https://stackoverflow.com/questions/4538209 that there is an undocumented--no-valign
option.Maybe the Perl style is to do all that vertical alignment, but to me it just looks old.
For the record, I installed
perltidy
in a dev ska env withcpanm Perl::Tidy
and this worked just fine.Interface impacts
None
Testing
Functional tests
Just regression.
Ran the standard starcheck set and saw no diffs. Ran the set we used for #402 in
https://icxc.cfa.harvard.edu/aspect/test_review_outputs/starcheck-pr405/
and see no diffs.