Support AllowAtMostNQubits operation to limit the number of qubits allocated in the code #1155
Assignees
Labels
enhancement
New feature or request
Comments
swernli
added a commit
that referenced
this issue
Jul 29, 2024
This introduces qubit count tracking APIs to the Diagnostics namespace that allow Q# code to get counts for how many unique qubits are used during a section of execution. This is useful in katas and auto-grading scenarios to verify that exercise restrictions are being appropriately followed. Fixes #1155
swernli
added a commit
that referenced
this issue
Aug 5, 2024
This introduces qubit count tracking APIs to the Diagnostics namespace that allow Q# code to get counts for how many unique qubits are used during a section of execution. This is useful in katas and auto-grading scenarios to verify that exercise restrictions are being appropriately followed. Fixes #1155
swernli
added a commit
that referenced
this issue
Aug 5, 2024
This introduces qubit count tracking APIs to the Diagnostics namespace that allow Q# code to get counts for how many unique qubits are used during a section of execution. This is useful in katas and auto-grading scenarios to verify that exercise restrictions are being appropriately followed. Fixes #1155
swernli
added a commit
that referenced
this issue
Aug 15, 2024
This introduces qubit count tracking APIs to the Diagnostics namespace that allow Q# code to get counts for how many unique qubits are used during a section of execution. This is useful in katas and auto-grading scenarios to verify that exercise restrictions are being appropriately followed. Fixes #1155
swernli
added a commit
that referenced
this issue
Aug 15, 2024
This introduces qubit count tracking APIs to the Diagnostics namespace that allow Q# code to get counts for how many unique qubits are used during a section of execution. This is useful in katas and auto-grading scenarios to verify that exercise restrictions are being appropriately followed. Fixes #1155
github-merge-queue bot
pushed a commit
that referenced
this issue
Aug 15, 2024
This introduces qubit count tracking APIs to the Diagnostics namespace that allow Q# code to get counts for how many unique qubits are used during a section of execution. This is useful in katas and auto-grading scenarios to verify that exercise restrictions are being appropriately followed. Fixes #1155
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Classic QDK supported AllowAtMostNQubits operation that restricted the number of qubits that could be allocated in the code.
This functionality was broadly used in the Quantum Katas, for example, to make sure the phase oracle is implemented without the phase kickback trick, or to limit the number of auxiliary qubits allocated by a reversible computing task. This is especially important in automatically graded programming assignments in which I really want to check whether the solution violates the requirements imposed by the task.
Describe the solution you'd like
A similar functionality in the modern QDK.
Describe alternatives you've considered
I don't have an alternative implementation for this functionality. In the classic QDK, there used to be a way to write a custom simulator that could do that that predated AllowAtMostNQubits, but this is not supported in the modern QDK.
The text was updated successfully, but these errors were encountered: