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.

Sign up for GitHub

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

Jump to bottom

Support OpenQASM 3.0 #3518

Closed
balopat opened this issue Nov 20, 2020 · 1 comment
Closed

Support OpenQASM 3.0 #3518

balopat opened this issue Nov 20, 2020 · 1 comment
Labels
area/qasm kind/feature-request Describes new functionality roadmap-candidate triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on

Comments

@balopat
Copy link
Contributor

balopat commented Nov 20, 2020

Currently we only support OpenQASM 2.0, we should start to look into what is required for exporting and importing to and from the new version of OpenQASM 3.0

What is the urgency from your perspective for this issue? Is it blocking important work?
P3 - I'm not really blocked by it, it is an idea I'd like to discuss / suggestion based on principle
@balopat balopat added kind/feature-request Describes new functionality area/qasm labels Nov 20, 2020
@balopat balopat added the triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on label Nov 30, 2020
@balopat balopat mentioned this issue Dec 1, 2020
Closed
@vtomole
Copy link
Collaborator

vtomole commented Oct 21, 2021

I will close this issue as a duplicate of #4509 even though this was the first one because the linked issue has more comments.

@vtomole vtomole closed this as completed Oct 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/qasm kind/feature-request Describes new functionality roadmap-candidate triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@balopat @vtomole