In 2 cases, made trivial use of NewInstance, so that it’s not unused.

Found via `codespell`

The code for ChangeExtent would only call SetExtent() if the Y or
Z values had changed.  If the only change was to X, then Extent
would not be modified.

- Changed some to be const also.
- Replaced others with call to ClampValue method.
- Changed some from int to bool.
- In a couple of cases the variable was unused, removed it.

Found via `codespell`

Found via `codespell`

vtkImageBlend was not blending images correctly in compound mode
for 2-channel (LA) and 1-channel images.
Test case has been added to test the compound mode, which
was previously missing.

Found via `codespell`

Change array syntax from pointer to dynamic array
Add size hints for dynamic arrays

This filter is most often to apply a Window/Level operation to
grayscale input data, without a lookup table, so I have put that
first in the description.  The less-common use of modulating the
color produced by a lookup table has been moved to the end.

Ken Martin authored 6 years ago and Brad King committed 6 years ago

make image difference symmetric to catch some
failures that were slipping through. This exposed
a number of valid images that were no longer
correct and needed to be replaced.

Kitware Robot authored 6 years ago and Brad King committed 6 years ago

Populate a script with `map_<md5>=<sha512>` variable settings and
then run the following to convert the content link files:

    git ls-files -- '*.md5' | while read f; do
      md5="$(cat "$f")"
      sha512="$(eval echo \${map_$md5})"
      rm "$f"
      echo $sha512 > ${f%.md5}.sha512
    done

The vtkImageResliceMapper was setting "Border" to 2, even though
the API suggests that it is meant to be boolean.  This commit adds
a new method called SetBorderThickness().

This new code ensures that the number of threads created will not
exceed the number of pieces that the data has been divided into,
so each thread will have at least some work to do.

It would probably be wise to go even further, and set a reasonable
minimum piece size so that fewer threads are allocated for smaller
images.

154 occurances of ;;\n

This required some clean up, because the automatic changes borked a couple of files, but mostly resulted in stupid whitespacing. A few find/replace fixed things up.

There are now some duplicate semis because it did changes like:

  ~AMRIndexIterator() override{};
to
  ~AMRIndexIterator() override= default;;

Note there was a pointless semi before, which clang-tidy didn’t expect / account for.

My next commit will remove them.

I was surprised how many there were.  But no bugs at least, as best as I could tell.

Removed a few useless semi-colons that were nearby.

Found via `codespell`

Found via `codespell`

includes grammar and uniformity fixes as well.