Skip to content

Conversation

@1tnguyen
Copy link
Collaborator

Description

This information was already populated for internal usage, e.g., to determine codegen spec, etc.
Now, expose it for downstream code to query it if needed (e.g., for validation purposes).

@1tnguyen 1tnguyen requested review from bmhowe23 and sacpis September 29, 2025 21:23
Copy link
Collaborator

@sacpis sacpis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks @1tnguyen.

@sacpis
Copy link
Collaborator

sacpis commented Sep 29, 2025

Should we add pybinding for get_target in cudaq/python/runtime/cudaq/target/py_runtime_target.cpp? So that it can be used in Python as well.

@1tnguyen
Copy link
Collaborator Author

Should we add pybinding for get_target in cudaq/python/runtime/cudaq/target/py_runtime_target.cpp? So that it can be used in Python as well.

In Python, the current cudaq.get_target() should provide target information (Python wrapper of the RuntimeTarget info) as well

github-actions bot pushed a commit that referenced this pull request Oct 15, 2025
@github-actions
Copy link

CUDA Quantum Docs Bot: A preview of the documentation can be found here.

@1tnguyen 1tnguyen merged commit 5efa9d2 into NVIDIA:main Oct 15, 2025
128 checks passed
github-actions bot pushed a commit that referenced this pull request Oct 15, 2025
@bettinaheim bettinaheim added the no release notes Don't list this PR in the release notes label Nov 25, 2025
@bettinaheim bettinaheim added this to the release 0.13.0 milestone Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no release notes Don't list this PR in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants