Provide a brief summary of the changes in this pull request, including relevant
motivation and context. List any dependencies required for this change. If this
pull request is related to an already identified issue or to-do note, please
link it using closes/fixes #issue-number or completes #todo-reference.
Please check all boxes that apply to the changes you introduced.
- Documentation update – Changes that affect documentation.
- Bug fix – A non-breaking change that fixes an issue.
- New feature – A non-breaking change that adds new functionality.
- Breaking change – A change that may break existing functionality (e.g., API modifications, major refactoring, etc).
Be sure you checked all boxes that apply.
- I have read and followed the Contributing Guidelines.
- I have linked the relevant issue/to-do note (if applicable).
- I have updated the changelog and todo documentation files.
- I have performed a self-review of my own code.
- I have added tests (where applicable).
- I have commented my code (where necessary).
- I have updated the documentation as needed.
- My changes generate no new warnings.
- New and existing unit tests pass locally with my changes.
- My code adheres to the coding style and guidelines of this project.
- My pull request targets a specific development branch, not the master one.
Provide any other relevant information related to this pull request. As an example, describe the tests you ran to verify your changes and provide detailed instructions for reviewers to reproduce the results. Additionally, justify any items in the above checklist that have not been checked.