Jake Lishman

The first point is because the metapackage pulls from its requirements, so it won't update until IBM Q provider puts out a new patch release, and we include it in...

I had had a similar thought about removing the `#`: I agree with everything Stefan just said. As a _potential_ reason for having it, though: pragmas do have slightly different...

Just for reference for everyone: I asked Lev to write out some examples of his concerns ahead of the types-and-casting group meeting. I'm planning to make his comment here the...

The implicit `{ }` on single statements are necessary for compatibility with OpenQASM 2, which doesn't have the braces at all. Once you have that, then `else if` is automatically...

There's no actual ambiguity in the language, because all our parsers (or parser generators) have associativity and precedence rules baked in. This particular one is an absolutely classic shift/reduce conflict,...

From your link (which I read before posting that comment), exactly under and example of `if x if y else z;`: > Bison is designed to resolve these conflicts by...

When you say "regular build/tests", what do you mean? How did you run the tests? It's quite possible an immediate workaround for you is to install `testtools` as an additional...

Yeah as it stands, `counts` will conflict with the default outputs (think `Result.get_counts`) in Aer and BasicAer. I expect you might get some weird behaviour if you use `"statevector"` or...

Yep, Azure hasn't rolled out the `noTags` item for us yet. I'll check in again in a couple of weeks.

Not available yet.