wrap comments at 80 columns - #2298
Merged
Merged
Conversation
Collaborator
Author
|
/ok to test 6b77805 |
ericniebler
force-pushed
the
wrap-comments
branch
from
October 3, 2026 16:08
6b77805 to
ae656ef
Compare
Collaborator
Author
|
/ok to test ae656ef |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
it isn't necessarily best to wrap code and comments at the same column limit. Code can sometimes become less readable when it gets broken across lines, so a longer column limit for code makes sense.
that's not the case for plain English, where long lines make large comment blocks less readable.
this PR leaves code wrapped at 100 columns but consistently wraps comment blocks at 80 columns.