-
**Describe the bug**
The first run of Python programs that import and use Q# packages via `qsharp.packages.add()` will emit a bunch of compilation errors during the `import qsharp` step, even if the …
-
**Describe the bug**
When the total number of return values from any _operation_ is more than 7 in qs code, then the python's _operation.simulate()_ returns `None`
**To Reproduce**
Steps to repro…
-
## 📚 Documentation
Many of programs in `C-Plus-Plus`, `C-Sharp`, `C`, `Go`, `Java`, `JavaScript`, `Python` and `Q-Sharp` are not linked to there respective README files. Go through the files and ch…
-
We need to formally define an IR format to compile into to facilitate a broader use. The expectation is that similarly to the compiler extensibility for transformations on top of the library format (s…
-
There is a circuit defined in the simulation tests here: https://github.com/microsoft/qsharp-runtime/blob/master/src/Simulation/Simulators.Tests/Circuits/Recursion.qs#L42
```
function GenRecursionPa…
-
As a part of _public class interface_ a const setter doesn't make much sense, whatever the implementation details of other methods might be. If clients outside of the class need to use the setter (for…
-
I noticed that we don't have any explanation (or at least that I could find) on the statement `within{} apply{}` used in some parts of our documentation (ej: https://docs.microsoft.com/en-us/quantum/u…
-
This program is accepted by the Q# compiler:
```
namespace Foo {
function Bar() : Unit { }
}
namespace Foo.Bar {
function Hello() : Unit { }
}
```
But it produces this C# compil…
-
In Microsoft.Quantum.Math package, when you call the PowI function with the exponent of -1, it throws a System.ArgumentOutOfRangeException.
**To Reproduce**
Steps to reproduce the behavior:
1. Wr…
-
**Suggestion**
We propose creating an analogue of `let` for qubits: a statement that allocates qubits and binds them to a name for the remainder of the current scope, after which the name is no lon…