Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add operation constraint to quantum extension #543

Merged
merged 2 commits into from
Sep 19, 2023
Merged

docs: add operation constraint to quantum extension #543

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
18845fd
docs: add operation constraint to quantum extension
ss2165 Sep 19, 2023
7065c20
remove semantic mapping constraint
ss2165 Sep 19, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 13 additions & 3 deletions specification/hugr.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1727,10 +1727,20 @@ allocation, and the compiler can add/remove/move these operations to use
more or fewer qubits. In some use cases, that may not be desirable, and
we may instead want to guarantee only a certain number of qubits are
used by the program. For this purpose TKET2 places additional
constraints on the `main` function that are in line with TKET1 backwards
compatibility. Namely the main function takes one `Array<N, Qubit>`
constraints on the HUGR that are in line with TKET1 backwards
compatibility:

1. The `main` function takes one `Array<N, Qubit>`
input and has one output of the same type (the same statically known
size). If further the program does not contain any `qalloc` or `qfree`
size).
2. All Operations that have a `FunctionType` involving `Qubit` have as
many `Qubit` input wires as output.


With these constraints, we can treat all `Qubit` operations as returning all qubits they take
in. The implicit bijection from input `Qubit` to output allows register
allocation for all `Qubit` wires.
If further the program does not contain any `qalloc` or `qfree`
operations we can state the program only uses `N` qubits.

### Higher-order (Tierkreis) Extension
Expand Down