Jake Lishman

I agree that qubits cannot be copied. It doesn't follow from that that two qubits put together into one identifier is not a register. In QASM, a register is an...

Sorry for the delay in getting back to you. This looks like it might be general problem in your Python environment, rather than an issue caused by Qiskit. You could...

This isn't the best way to go about this - see https://github.com/Qiskit/qiskit/issues/1497#issuecomment-1147475790 for an alternative approach.

Hi Noah, QASM 3 as a language already supports all the IEEE 754 floating-point types (the names are `float[16]`, `float[32]`, ..., `float[256]` for half-, single-, ..., and octuple-precision). The question...

I think I have a couple more questions to ask before I can have a proper opinion on it. Sorry this is long - I've laid out how I understand...

Yeah, ok, those are the answers I thought, thanks. Yeah, I totally agree that any _real_ implementation won't completely separate out the two parsing bits there, because I can only...

Yeah, actually swapping the "default" branch on GitHub is very easy, the extra bits are just making sure that all our hyperlinks point to the new default branch. That's a...

This repository is not primarily a Python package, and the Makefile in the root is purely for helping to build the live specification of the OpenQASM 3 web page. It...

+1 from me. Playing the other side: a grammar is never going to give you all the information about any given identifier; some of that will always come from semantic...

@taalexander: I think this might be a minor difference between OpenQASM 3 and OpenPulse - I think in the OpenPulse spec, you can use (say) `$q` as a wildcard pattern:...