avoid spurious single-line commas #75
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Somewhat defensively, nph was putting a comma on a new line after certain complex constructs, in particular when using a complex expression in a parameter list - it turns out that this comma can stay on the same line most of the time, as long as an `nkCommand` is not involved
arnetheduck
force-pushed
the
single-comma
branch
from
a7470ae
to
c6b59ca
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Somewhat defensively, nph was putting a comma on a new line after certain complex constructs, in particular when using a complex expression in a parameter list - it turns out that this comma can stay on the same line most of the time, as long as an
nkCommandis not involved