- 
        Couldn't load subscription status. 
- Fork 706
Inputs can be provided from python to QASM 3.0 programs #7651
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- more general Casts - no special handling for Literals - catch no-else-return lint error - context initialization order
Co-authored-by: Astral Cai <[email protected]>
- error types - helper function - docstring
Co-authored-by: Christina Lee <[email protected]>
- ranges and index expressions
| Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@           Coverage Diff           @@
##           master    #7651   +/-   ##
=======================================
  Coverage   99.68%   99.68%           
=======================================
  Files         543      543           
  Lines       55347    55360   +13     
=======================================
+ Hits        55173    55186   +13     
  Misses        174      174           ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
 | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. One blocking comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Context: We would like to be able to declare inputs in QASM 3.0 and pass values for these inputs to
interpret()Description of the Change: We allow additional kwargs to be passed to
from_qasm3()andinterpret()which populate input variables declared in the program.Benefits: We can parameterize circuits easily.
Possible Drawbacks: The approach does not involve a compilation step like is suggested in the OpenQASM 3.0 docs here: spec.
Related ShortCut Stories: [sc-91127]