Currently, most samples only have a C# host program. It would be nice if more or even most samples demonstrated how to use Python to call into Q#.

Samples with Python Hosts

• algorithms
  • chsh-game
  • database-search
  • integer-factorization
  • oracle-synthesis
  • order-finding
  • reversible-logic-synthesis
  • simple-grover

• arithmetic

The katas offer a set of programming exercises on quantum computing and reference solutions to them, but we often hear that it would be helpful to have the solutions explained, with the logic steps necessary to arrive from the problem description to the code spelled out. It is especially important for people who go through the katas on their own, without a study group to support them.

To addres

What is the expected enhancement?

I have found a decorator of this form very useful for constructing pulse experiments from functions.

I suggest macro to represent a python function with an activated builder conte

Currently MatrixGate plots an entire matrix when displayed in a circuit. For single qubit gates this is usually OK, but for two qubit gates the gates end up being pretty monstorous. I've taken to hacking circuit_diagram_info in this case, but I think it would be nice if there was a way to do this at construction time, i.e.
cirq.MatrixGate(u, circuit_diagram_info=lambda or diagram info)

To get this codebase up to standard, we need to add type hints. At the very least, perhaps we should start insisting that all new code has type hints added, but moreover we need to add typing to the code that currently exists.

This is a pretty large project, but luckily it can be done incrementally - I believe at this point it's a stretch goal for v1, if anyone wants to help it would be much ap

Running travis lint gives a bunch of warning. Like for instance, sudo : required is no longer needed, and Travis migrated to a new architecture. So the travis.yml file needs to be updated.

https://blog.travis-ci.com/2018-10-04-combining-linux-infrastructures

For example, pylint would have caught ProjectQ-Framework/ProjectQ#19 via an undefined variable warning.

What is the expected enhancement?

>>> from qiskit.aqua.operators import I, X
>>> (0 * X + I) == I
False  # should be True

A possible solution would be to add a ``SummedOp.chop_summands(threshold=0)

Repro:

(describe #'COMMUTE-RZ-AFTER-CPHASE)

Output:

#<COMPILER COMMUTE-RZ-AFTER-CPHASE {10149CF36B}>
  [funcallable-instance]


Lambda-list: (X Y &KEY CONTEXT)
Derived type: (FUNCTION (T T &KEY (:CONTEXT T)) (VALUES T &OPTIONAL))
Documentation:
  T
Source file: quilc/src/compressor/rewriting-rules.lisp

Slots with :INSTANCE allocation:
  NAME                           

It looks like the upcoming sbcl 2.0.1 release includes changes to move certain symbols out of cl:*features* and into sb-impl:+internal-features+ [[1]]. IIUC, any "non-public" features will continue to work (for now), but issue a warning [[2]].

I haven't tested it, but it looks like we use at least one such soon-to-be-deprecated feature, namely avx2. We should figure out what to do about