-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Support "input" modifier in QASM3 parser #7933
Copy link
Copy link
Closed
Labels
area/qasmhelp wantedContributors welcomeContributors welcomekind/feature-requestDescribes new functionalityDescribes new functionalitytriage/acceptedA consensus emerged that this bug report, feature request, or other action should be worked onA consensus emerged that this bug report, feature request, or other action should be worked on
Metadata
Metadata
Assignees
Labels
area/qasmhelp wantedContributors welcomeContributors welcomekind/feature-requestDescribes new functionalityDescribes new functionalitytriage/acceptedA consensus emerged that this bug report, feature request, or other action should be worked onA consensus emerged that this bug report, feature request, or other action should be worked on
Is your feature request related to a use case or problem? Please explain
This is a limited-scope follow-up to #7908 - the PR which initially intended to enhance QASM parser with a support for parameterized gates.
Describe the solution you would prefer
OpenQASM3 allows parameterized gates with the
inputmodifier. Here is a minimum example that imports as parameterized circuit in Qiskit:It would be nice to have it working in Cirq too and produce gates with appropriately named symbolic parameter(s):
The QasmParser needs to learn
float,angle, andinputkeywords as appropriate for QASM3 vs QASM2 language versions. This should be done with a minimum intrusion to the QasmParser code and with care to keep, if possible, existing API interfaces unchanged.How urgent is this for you? Is it blocking important work?
P3 – I'm not really blocked by it; it's an idea I'm proposing based on principle
PS: I am not sure how much need is there for this feature. The priority can be increased if we get upvotes here.