Jake Lishman

This is being deferred to 1.1 along with the rest of the `Var` and `Store` handling. The PR as written depends on #11666 for its tests to pass, because the...

Huh, I forgot I'd already made this PR. Anyway, I rebased this branch over main, cherry-picked in #11820 and #11666 which are required, and I'll rebase them out again once...

Now rebased over all necessary fixes.

I believe this should be fixed by #12776, but since I can't generate the exact initial circuit to check, I'm not absolutely 100% sure. I'll mark it as "being fixed",...

> Does anyone know how we would give some kind of deprecation warning when `from qutip import *` is made to say that only core functions will be imported from...

This all sounds logical to me. I think the killer for NFKC is the handling around the variants of things like `\phi`/`\varphi` - they may technically be the same letter,...

Is the intent to apply package versions like `3.0.x` to the `openqasm3` package on PyPI? If so, I'm not sure it's right - a parser's version isn't typically tied to...

I'd be fine to split the repos and move `openqasm3` somewhere else; I'm not convinced that `openqasm3` _should_ be in this repo, but at the time a couple of years...

> I'm still new here. That doesn't make your opinion any less valid than mine! If nothing else, you've been in the TSC meetings recently and I haven't been for...

This is going to be true of any grammatically invalid program, not just this case. It's not easy to build a parser that gives good error messages, and here ANTLR...