Proposed PR branch: qe/issue-07-transform-typed-wrappers
Category: Feature Request (usability + safer integration surface)
Problem
- Transform entry points are easy to misuse from integrations.
- Typed wrappers reduce caller mistakes and simplify language bindings.
Justification / why this is needed
- Many consumers call zDNN from C++ and higher-level runtimes (Python, Rust,
Java, etc). Varargs/loosely-typed inputs complicate safe bindings.
- Typed wrappers reduce the chance of mixing up descriptor/format parameters
and make call sites self-documenting.
- This is purely additive/opt-in and does not remove existing APIs.
Proposed change
- Add typed wrappers for FICO and ZRH gate inputs.
- Add dedicated tests.
- (Optional follow-up) Add README examples once the code changes are merged upstream.
Acceptance criteria
- New typed wrapper APIs are exported.
- Existing APIs remain supported.
- Tests cover expected behavior and invalid input handling.
Test plan
make test (expects tests/testDriver_transform_typed_wrappers.c to pass).
References
- Key files:
zdnn/stickify.c, zdnn/zdnn.h, zdnn/zdnn.map,
tests/testDriver_transform_typed_wrappers.c.
Proposed PR branch:
qe/issue-07-transform-typed-wrappersCategory:
Feature Request(usability + safer integration surface)Problem
Justification / why this is needed
Java, etc). Varargs/loosely-typed inputs complicate safe bindings.
and make call sites self-documenting.
Proposed change
Acceptance criteria
Test plan
make test(expectstests/testDriver_transform_typed_wrappers.cto pass).References
zdnn/stickify.c,zdnn/zdnn.h,zdnn/zdnn.map,tests/testDriver_transform_typed_wrappers.c.