quantum-computing

In prebuild script used by the Binder, we try to do dotnet build on all katas and tutorials listed in https://github.com/microsoft/QuantumKatas/blob/main/Dockerfile, regardless of whether they actually have a .csproj file to build:
https://github.com/microsoft/QuantumKatas/blob/a8437af4a1a06d24e6dd0bf915acaef0a4f0a045/scripts/prebuild-kata.sh#L7

We have several tutorials, ComplexArithmetic a

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

What is the expected enhancement?

Currently, accessing the preset passmanagers (outside of a call to transpile) requires building a pass_manager_config by hand, like:

from qiskit.transpiler import PassMan

As discussed with @tanujkhattar in #4362, creating a separate issue to track GateTabulation refactoring.

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

Is your feature request related to a problem? Please describe.
I would like to check the behavior of the parameter index in the function QubitCircuit.add_gate()

In qutip.qip.QubitCircuit.add_gate(), there is a optional list type attribute called index.
This seems to be used to insert gates in the middle of the gate list (qutip.qip.QubitCircuit.gates).
The corresponding code is

Currently, the operation MultiControlledX accepts an arbitrary length of wires for control_wires keyword and a single wire for the wires keyword:

qml.MultiControlledX(control_wires=(0,1,2,3), wires=4)

We should instead be able to create this

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

In QASM2, the BNF listed a set of buit-in unary functions,sin j cos j tan j exp j ln j sqrt. However, it was not explicit on their meaning.

QASM3 specification does not list (as far as I could check) the built-in functions and their meaning and I think it should.

Describe the issue
Some of the code cells in the Japanese translation of the textbook are outdated and might not work with the latest version of Qiskit. These files need to be updated by a Japanese speaker to match the English version of the textbook (under i18n/locales/ja/):

• ch-algorithms/shor.ipynb
• ch-algorithms/defining-quantum-circuits.ipynb
• `ch-algorithms/sim

Is your feature request related to a problem? Please describe.
Adding concrete examples to API documentation comments can help clarify how Q# functions and operations are to be used. For example, the documentation for Microsoft.Quantum.Arrays.ElementsAt lists how the function acts on a variety of arrays:

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