-
I've noticed myself often implementing `body` blocks exactly as follows:
```
body (...) {
Controlled this_operation(new Qubit[0], (arguments))
}
```
which significantly reduces code dupl…
-
Currently, when you want to allocate several registers, it is quite cumbersome. You get a lot of indentation, you have to assign temporary names to the raw register before wrapping it into the type yo…
-
**Is your feature request related to a problem? Please describe.**
The `Range` type effectively acts as a UDT, in that it consists of three `Int` values. Unlike UDTs, however, `Range` values cannot b…
-
**Describe the bug**
After typing `@`, typing a letter or pressing Ctrl+Space shows completions for all identifiers and keywords, not just attribute names.
**To Reproduce**
Steps to reproduce…
-
**Describe the bug**
The new `@EntryPoint` attribute does not take structured arguments (sensibly) as it is intended to work with command line applications. However, if I am using an `@EntryPoint` …
-
If I type a function from a namespace that's not opened, the editor will auto-insert "open" statement for me. However, if I copy/paste the same function, it won't auto-insert that open statement, whic…
-
**Is your feature request related to a problem? Please describe.**
With resolving #35 in April, we made a lot of progress on making the libraries more consistent, more discoverable, and easier to use…
-
**Describe the bug**
When serializing values of type `Range` as returned by a function or operation, the serializer expands the `Range` into an array of its values:
![image](https://user-images.gi…
-
When writing arithmetic functions, it seems common to have variants specialized to `int`, `BigInt`, and `LittleEndian`. It's confusing to have to remember different names for these functions, instead …
-
**Is your feature request related to a problem? Please describe.**
When writing a polymorphic function in Q#, the type variables are fully general. They are opaque types with no properties that the f…