Several katas could have better error messaging:

• Superposition : the test harness could log the actual state of the system after prep vs the expected state before asserting that they are the same (the change would add state prep and logging using DumpMachine to AssertEqualOnZeroState)
• BasicGates : a similar improvement, but a bit more extra code to write a unified test wrapper

Here are some examples:

• Root README is missing machine learning category of samples
• README in algorithms is missing repeat-until-success and sudoku-grover
• [README in diagnostics](https://github.com/microsoft/Quantum/blob/main/samples/diagnostics/RE

Information

• Qiskit Terra version: '0.18.0.dev0+98130dd'
• Python version: 3.8
• Operating system: Windows

What is the current behavior?

The InstructionScheduleMap allows to add callable schedules. This works for normal callab

Description of the issue

SingleQubitCliffordGates write incomplete information to JSON, and their type cannot be understood by the JSON deserializer.

How to reproduce the issue

>>> import cirq
>>> print(cirq.__version__)
0.10.0
>>> q = cirq.LineQubit(0)
>>> json_text = cirq.to_json(cirq.SingleQubitCliffordGate.X(q))
>>> print(json_text)
{
  "cirq_type": "GateOp

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

Describe the bug
qutip.random_objects.rand_ket does not work as intended
rand_ket(N=0, density=1, dims=None, seed=None) should be to figure out what N is, given dims is assigned when N is set to be 0 or None.

To Reproduce

from qutip.random_objects import rand_ket
rand_ket(None, dims=[[2],[1]])

The terminal out put is

-----------------------------------------

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

Describe the bug
If I provide Partitioned an array of length N and partition sizes of total length N, the return contains an extra partition of length 0 in the end. This makes it inconvenient to use: if I want to split an array into K parts of equal length ([example](https://github.com/microsoft/Quantum

There seems to be confusion between 'schedule' and 'scheduler' throughout sources and doc. They seem to be used interchangeably, which seems confusing. Is a "schedule" the same as a "scheduleR"?

For example, consider the following code snippet in src/compressor/compressor.lisp:

  (let ((lschedule (make-lscheduler)))
    ;; load up the logical schedule

The variable lschedule and