Include line diff in numdiff output #1164
Merged
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.
When running tests, if Numdiff is used only the differing values and their position in the lines in question are shown in the generated diff files. This results in having to either visually do the comparison, use another diff tool or redoing the diff using "numdiff -V" in order to obtain the context of the variations between the two. The change made is to use "numdiff -V" when generating the DIFF_OUTPUT intended to become *.diff or *.diff.failed in order to also include the originating lines when printing the diff.
Is not making use of this flag an intended design decision, a compatibility limitation, or was the capability overlooked?