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
I inspected the EOL-CR+LF.md and EOL-LF.md in a hex editor as per your note, and these files are identical, as far as I can tell - and they both appear (on github.com) to be precisely 119 bytes, which, if one has CR+LF bytes for line breaks, it should have slightly more bytes than the one that has only LF bytes, correct?
Perhaps your IDE or some other tool, at some point, cleaned up what was deliberately intended to be leading/trailing space for test purposes?
I hope this is helpful :-)
The text was updated successfully, but these errors were encountered:
On a related note, if you want to make sure the files are checked out (and commited) as-is, you should probably add a .gitattributes file with a line like *.md -text - and probably *.out -text as well, if you want to make sure people check out the files correctly, so that tests produce the same results regardless of Git user preferences on each system.
I can understand duplicating certain tests when there is overlap between two test-suites:
But what's the purpose of tests duplicated within the same test-suite?
I inspected the
EOL-CR+LF.md
andEOL-LF.md
in a hex editor as per your note, and these files are identical, as far as I can tell - and they both appear (on github.com) to be precisely 119 bytes, which, if one has CR+LF bytes for line breaks, it should have slightly more bytes than the one that has only LF bytes, correct?Perhaps your IDE or some other tool, at some point, cleaned up what was deliberately intended to be leading/trailing space for test purposes?
I hope this is helpful :-)
The text was updated successfully, but these errors were encountered: