-
Notifications
You must be signed in to change notification settings - Fork 312
Issues: openqasm/openqasm
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Array references should accept default GH label
PositiveInt
enhancement
#549
opened Aug 29, 2024 by
TheGupta2012
Consider allowing for default GH label
defcal
to be parameterized by classical types
enhancement
#547
opened Aug 7, 2024 by
braised-babbage
Errors in the standard library documentation
documentation
Documentation other than the text of the spec
#545
opened Jul 30, 2024 by
projekter
Release notes page is empty
documentation
Documentation other than the text of the spec
#544
opened Jul 12, 2024 by
garrison
Clarify relationship between default GH label
bit
, bit[1]
and bool
enhancement
#535
opened Apr 30, 2024 by
jakelishman
Clarify spelling of the default GH label
bit
literal
enhancement
#534
opened Apr 30, 2024 by
jakelishman
Clarify whether arrays and bit registers of size 0 are allowed
enhancement
default GH label
#532
opened Apr 24, 2024 by
garrison
Allowed casting for classical types is non-transitive
documentation
Documentation other than the text of the spec
#527
opened Apr 8, 2024 by
ajberdy
Add doctest-like infra for checking examples in the spec are correct
CI
Continuous integration
enhancement
default GH label
#526
opened Apr 3, 2024 by
levbishop
Include list of reserved identifiers (keywords) in the written spec
#524
opened Mar 25, 2024 by
jlapeyre
Support Semantic changes to language, not clarification
extern
gate declarations
enhance/change spec
#507
opened Jan 13, 2024 by
jlapeyre
Clarify semantics of Change text of spec, not (mainly) semantics of spec
bit
and qubit
arrays
clarify specification
#494
opened Nov 17, 2023 by
jlapeyre
Clarify semantics of Semantic changes to language, not clarification
input
and output
enhance/change spec
#493
opened Nov 17, 2023 by
jlapeyre
Clarify the purpose and/or remit of the Technical Steering Committee
TSC
Technical Steering Committee
#489
opened Nov 8, 2023 by
jlapeyre
Make array reference types first-class
enhance/change spec
Semantic changes to language, not clarification
#483
opened Oct 6, 2023 by
braised-babbage
Grammar/AST does not support assignment with defined measurements
bug
enhance/change spec
Semantic changes to language, not clarification
Reference Parser
ANLTR-based Python reference parser
#481
opened Oct 4, 2023 by
braised-babbage
Classical Compound Assigment Operators insufficiently documented
clarify specification
Change text of spec, not (mainly) semantics of spec
#478
opened Aug 29, 2023 by
jwoehr
visitIODeclaration does not support arrayType
bug
Reference Parser
ANLTR-based Python reference parser
#474
opened May 25, 2023 by
menna-atlantic
Clarify whether defcals can be defined using aliases
clarify specification
Change text of spec, not (mainly) semantics of spec
#472
opened May 10, 2023 by
amilsted
[rangeExpression] Clarification needed
clarify specification
Change text of spec, not (mainly) semantics of spec
#469
opened May 1, 2023 by
nelimee
[Pragmas]: Improvements in documentation and specification
clarify specification
Change text of spec, not (mainly) semantics of spec
Reference Parser
ANLTR-based Python reference parser
#468
opened Apr 25, 2023 by
nelimee
Notation Change text of spec, not (mainly) semantics of spec
s:m:f
appears too early in the documentation
clarify specification
#467
opened Apr 13, 2023 by
nelimee
Determine the proper way to claim copyright for this project.
enhancement
default GH label
#466
opened Apr 12, 2023 by
mbhealy
[AST / Documentation] Unclear specification for the barrier instruction
clarify specification
Change text of spec, not (mainly) semantics of spec
#461
opened Apr 3, 2023 by
nelimee
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.