You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 8, 2024. It is now read-only.
I observe that PR#169 includes a trivial change to the last line of particular files that does not affect the parsing of that file.
In one version, the line ends with a newline. In the other, it ends with the end-of-file and no terminating new-line.
Basically, this is the difference in having the newline character be a line separator or having it be the terminal character of each line.
I would prefer that one, or the other, convention be used throughout.
In particular, I suggest that we not have a filter that allows both, thus failing to flag trivial changes from one form to the other.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I observe that PR#169 includes a trivial change to the last line of particular files that does not affect the parsing of that file.
In one version, the line ends with a newline. In the other, it ends with the end-of-file and no terminating new-line.
Basically, this is the difference in having the newline character be a line separator or having it be the terminal character of each line.
I would prefer that one, or the other, convention be used throughout.
In particular, I suggest that we not have a filter that allows both, thus failing to flag trivial changes from one form to the other.
The text was updated successfully, but these errors were encountered: