Throw a warning for use of unsupported draw API on hardware targets.
#3318
Conversation
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
khalatepradnya
force-pushed
the
warn-draw
branch
from
4fe8b35 to
9002d5b
Compare
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Signed-off-by: Pradnya Khalate <[email protected]>
khalatepradnya
force-pushed
the
warn-draw
branch
from
4c6bfe8 to
f57cb37
Compare
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Pull request was converted to draft
|
Converting back to draft to finish some internal discussion. |
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
|
@bettinaheim - Please confirm if this is ready to go. |
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
3 participants
This PR improves the usability and robustness of the
drawfunction in the CUDA-Q, specifically handling cases where the function is invoked on hardware backends instead of simulators. The changes ensure that users receive a warning and an empty result rather than an exception. Also update the docs to clarify that this is simulator-only feature.