We're close to having full-path QPY in Rust. At that point, we can also expose it to C, which will simplify downstream provider packages (like qiskit-ibm-runtime-c) and make it far easier to get complex circuits into C space.
Depends on #15662.
Related to #15976; that issue isn't technically required to add the functionality, but we largely need it in order for it to be safe to call QPY downstream.
We're close to having full-path QPY in Rust. At that point, we can also expose it to C, which will simplify downstream provider packages (like
qiskit-ibm-runtime-c) and make it far easier to get complex circuits into C space.Depends on #15662.
Related to #15976; that issue isn't technically required to add the functionality, but we largely need it in order for it to be safe to call QPY downstream.