You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a tracking issue for monitoring the capabilities of Qiskit's C-API (https://quantum.cloud.ibm.com/docs/en/api/qiskit-c) as an alternative for exchanging circuits between the MQT Core IR and Qiskit that does not rely on Python.
Describe the solution you'd like
According to the Qiskit development roadmap (https://github.com/Qiskit/qiskit/wiki/Roadmap), an API for circuit construction will likely land with Qiskit 2.1 in June 2025
A corresponding PR is open at Qiskit/qiskit#14006.
Once that is in, the MQT could start exploring how we could interoperate with Qiskit on that level.
The text was updated successfully, but these errors were encountered:
What's the problem this feature will solve?
This is a tracking issue for monitoring the capabilities of Qiskit's C-API (https://quantum.cloud.ibm.com/docs/en/api/qiskit-c) as an alternative for exchanging circuits between the MQT Core IR and Qiskit that does not rely on Python.
Describe the solution you'd like
According to the Qiskit development roadmap (https://github.com/Qiskit/qiskit/wiki/Roadmap), an API for circuit construction will likely land with Qiskit 2.1 in June 2025
A corresponding PR is open at Qiskit/qiskit#14006.
Once that is in, the MQT could start exploring how we could interoperate with Qiskit on that level.
The text was updated successfully, but these errors were encountered: