---
name: "Design Impact Report \U0001F680"
labels: type:Design
about: "File a design report to improve ITK design"
---

<!-- The text within this markup is a comment, and is intended to provide
guidelines to open an issue for the ITK repository. This text will not
be part of the issue. -->


<!-- Before submitting an issue, please check that your issue has not been
already filed. -->

### Description

<!-- Description of the impact of the current design in terms of ease-of-use, or
intuitiveness, and how a change in design would benefit the toolkit. -->

### Impact analysis

<!-- Detailed analysis of the benefits/downsides of the current design, and the
benefits/downsides of the proposed design. -->

### Expected behavior

<!-- What you expect the design to be. Include a snippet of what the code would
look like. -->
```none
```

<!-- 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,
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. -->

### Actual behavior

<!-- What the actual design is. Include a snippet of what the actual code looks
like. -->
```none
```

### Versions

<!-- If a tagged version, you can get this information by inspecting the
`ITK_VERSION_MAJOR` `ITK_VERSION_MINOR` and `ITK_VERSION_PATCH` variable
values in the `ITKConfig.cmake` file.

If the commit number is required, run `$ git rev-parse --short HEAD`. -->

### Additional Information

<!-- Any additional information, configuration or data that might be necessary
to reproduce the issue. -->


<!-- **Note**: Use issues for their purpose; issues are not for code help. Need
help? Ask your question at ITK discourse (https://discourse.itk.org/). -->