Skip to content
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

Support more OpenQASM 2.0 gates from qelib1.inc #7072

Open
pavoljuhas opened this issue Feb 19, 2025 · 1 comment
Open

Support more OpenQASM 2.0 gates from qelib1.inc #7072

pavoljuhas opened this issue Feb 19, 2025 · 1 comment
Labels
area/qasm kind/feature-request Describes new functionality triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on

Comments

@pavoljuhas
Copy link
Collaborator

Is your feature request related to a use case or problem? Please describe.

This is a follow-up to #7007, which reported qasm parser failure for identifiers starting with gate.
After the fix in #7018 the example code still fails because of unknown rzz gate.

Describe the solution you'd like

Support parsing of more QASM gates from "qelib1.inc".
At the very least we should add gates that have a direct counterpart in cirq.

What is the urgency from your perspective for this issue? Is it blocking important work?

P2 - we should do it in the next couple of quarters

@pavoljuhas pavoljuhas added the kind/feature-request Describes new functionality label Feb 19, 2025
@pavoljuhas pavoljuhas added area/qasm triage/discuss Needs decision / discussion, bring these up during Cirq Cynque labels Feb 19, 2025
@NoureldinYosri NoureldinYosri removed the triage/discuss Needs decision / discussion, bring these up during Cirq Cynque label Mar 5, 2025
@mhucka mhucka added the triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on label Mar 5, 2025
@mhucka
Copy link
Contributor

mhucka commented Mar 5, 2025

Discussed in Cirq Cynq 2025-03-05: not highly urgent, but should be done & seems fairly easy to address.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/qasm kind/feature-request Describes new functionality triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on
Projects
None yet
Development

No branches or pull requests

3 participants