Jake Lishman

Thank you so much for this! I know it's probably not the biggest priority, but it'll be great to have it.

Oh boy - "A `EquivalenceLibrary`" haha. No points for English for me.

I'm still interested in seeing it (for example, I'd use it to make https://docs.quantum.ibm.com/api/qiskit/qasm2#legacy-compatibility prettier), but it's really not important. "Next year" isn't a deal breaker. I can throw up...

The times you're seeing an empty message are when the underlying ANTLR parser is failing, and the cases that have messages are when the conversion to Qiskit that is actually...

I agree with you - this is actually one of the reasons we're moving away from this thin wrapper package to replace it with a more in-house OpenQASM 3 parser:...

Thanks for the report - looks like I made mistake with the typing of the `pi` built-in, and also that there's no promotion rules from `angle` to `float` in the...

Yeah, it's kind of deliberate at the moment (hence the error message) - Terra doesn't have support for representing any sort of non-const `uint` runtime value, so I had the...

I think I originally made the decision to reject this because the Terra exporter's handling of subroutine outputs was really pretty questionable (if I remember correctly). The problems we'd face...

There's a couple of things going on here. First, the `repr` method of `Instruction` misleading always writes `Instruction(...)` and ignores the type. As things happen, the OQ2 importer returns a...

There's no timeline at the moment. We had originally intended to do this sooner rather than later (and that's what https://github.com/Qiskit/openqasm3_parser) is about, but very shortly after the Qiskit 1.0...