Merge branch 'main' into fix_jac_determinant

Author: hjmjohnson

.circleci/config.yml

@@ -297,6 +297,7 @@ StatementMacros:
   - ITK_CLANG_PRAGMA_PUSH
   - ITK_CLANG_PRAGMA_POP
   - ITK_CLANG_SUPPRESS_Wzero_as_null_pointer_constant
+  - ITK_CLANG_SUPPRESS_Wduplicate_enum
   - CLANG_PRAGMA_PUSH
   - CLANG_PRAGMA_POP
   - CLANG_SUPPRESS_Wfloat_equal

.clang-format

@@ -0,0 +1,14 @@
+## Outcome configuration based on defaults,
+# yaml-language-server: $schema=https://raw.githubusercontent.com/BlankSpruce/gersemi/0.19.3/gersemi/configuration.schema.json
+
+definitions: [ "CMake/stubs" ]
+disable_formatting: false
+extensions: []
+# default is indent of 4, ITK uses 2
+indent: 2
+line_length: 80
+# default is list_expansion: favour-inlining
+list_expansion: favour-expansion
+unsafe: false
+# default is warn_about_unknown_commands: true
+warn_about_unknown_commands: false

.clang-tidy

@@ -24,8 +24,8 @@ already filed. -->
 3. [and so on...]
 
 Provide a minimal, complete, compilable, and verifiable example (commonly
-abbreviated as MWE, Minimal Working Example, or sometimes referred to as SSEE,
-Short, Self Contained, Correct (Compilable) Example, SSCCE) or code snippet,
+abbreviated as MWE, Minimal Working Example, or sometimes referred to as SSCCE,
+Short, Self Contained, Correct (Compilable) Example) or code snippet,
 either through a GitHub gist (https://gist.github.com/) or providing your own
 files (including your source code, `CMakeLists.txt` file if applicable, and your
 data) reproducing the issue or showing an incorrect result. -->

.gersemi.config

@@ -24,8 +24,8 @@ already filed. -->
 3. [and so on...]
 
 Provide a minimal, complete, compilable, and verifiable example (commonly
-abbreviated as MWE, Minimal Working Example, or sometimes referred to as SSEE,
-Short, Self Contained, Correct (Compilable) Example, SSCCE) or code snippet,
+abbreviated as MWE, Minimal Working Example, or sometimes referred to as SSCCE,
+Short, Self Contained, Correct (Compilable) Example) or code snippet,
 either through a GitHub gist (https://gist.github.com/) or providing your own
 files (including your source code, and `CMakeLists.txt` file) reproducing the
 build failure. -->

.github/ISSUE_TEMPLATE/bug_report.md

@@ -25,8 +25,8 @@ data benefits or challenges the toolkit. -->
 3. [and so on...]
 
 Provide a minimal, complete, compilable, and verifiable example (commonly
-abbreviated as MWE, Minimal Working Example, or sometimes referred to as SSEE,
-Short, Self Contained, Correct (Compilable) Example, SSCCE) or code snippet,
+abbreviated as MWE, Minimal Working Example, or sometimes referred to as SSCCE,
+Short, Self Contained, Correct (Compilable) Example) or code snippet,
 either through a GitHub gist (https://gist.github.com/) or providing your own
 files (including your source code, `CMakeLists.txt` file if applicable, and
 your data) showing how the toolkit is challenged by the new data. -->

.github/ISSUE_TEMPLATE/compiler_support_report.md

@@ -30,8 +30,8 @@ look like. -->
 ```
 
 <!-- Provide a minimal, complete, compilable, and verifiable example (commonly
-abbreviated as MWE, Minimal Working Example, or sometimes referred to as SSEE,
-Short, Self Contained, Correct (Compilable) Example, SSCCE) or code snippet,
+abbreviated as MWE, Minimal Working Example, or sometimes referred to as SSCCE,
+Short, Self Contained, Correct (Compilable) Example) or code snippet,
 either through a GitHub gist (https://gist.github.com/) or providing your own
 files (including your source code, `CMakeLists.txt` file if applicable, and your
 data) showing the benefit of the change. -->

.github/ISSUE_TEMPLATE/data_addition_request.md

@@ -30,8 +30,8 @@ code would look like. -->
 ```
 
 <!-- Provide a minimal, complete, compilable, and verifiable example (commonly
-abbreviated as MWE, Minimal Working Example, or sometimes referred to as SSEE,
-Short, Self Contained, Correct (Compilable) Example, SSCCE) or code snippet,
+abbreviated as MWE, Minimal Working Example, or sometimes referred to as SSCCE,
+Short, Self Contained, Correct (Compilable) Example) or code snippet,
 either through a GitHub gist (https://gist.github.com/) or providing your own
 files (including your source code, `CMakeLists.txt` file if applicable, and your
 data) showing the benefit of the change. -->

.github/ISSUE_TEMPLATE/design_impact_report.md

@@ -30,8 +30,8 @@ what the code would look like. -->
 ```
 
 <!-- Provide a minimal, complete, compilable, and verifiable example (commonly
-abbreviated as MWE, Minimal Working Example, or sometimes referred to as SSEE,
-Short, Self Contained, Correct (Compilable) Example, SSCCE) or code snippet,
+abbreviated as MWE, Minimal Working Example, or sometimes referred to as SSCCE,
+Short, Self Contained, Correct (Compilable) Example) or code snippet,
 either through a GitHub gist (https://gist.github.com/) or providing your own
 files (including your source code, `CMakeLists.txt` file if applicable, and your
 data) that shows the performance improvement of the change. -->