-
Notifications
You must be signed in to change notification settings - Fork 91
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.
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
Track qubit live-ness during simulation #2020
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change adds some basic qubit live-ness tracking to the simulator, achieved by changing the `Value::Qubit` variant to a weak pointer to the qubit and having the execution environment own and track the `Rc` that owns the qubit. This provides a few benefits: - Fixes a panic when a qubit is passed to the simulator after it has been released. - Adds graceful error handling to treat use-after-release as a runtime error. - Adds a specific error for "double release" of a qubit if it is being manually managed. - Updates the display of the qubit type to show the qubit ID when it is live and `Qubit<released>` when it is not, enabling easier debugging of qubit lifetimes. Of note, local perf testing showing no impact on performance (thanks, Rust zero-cost abstractions!), though it stands to reason this change could theoretically have some impact on programs that use many thousands of qubits.
swernli
requested review from
billti,
ivanbasov,
idavis and
minestarks
as code owners
November 13, 2024 19:12
minestarks
reviewed
Nov 13, 2024
minestarks
approved these changes
Nov 14, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
live-ness
I feel like the word you're looking for is "lifetime"?
sezna
reviewed
Nov 14, 2024
sezna
reviewed
Nov 14, 2024
sezna
reviewed
Nov 14, 2024
sezna
reviewed
Nov 14, 2024
sezna
reviewed
Nov 14, 2024
sezna
reviewed
Nov 14, 2024
sezna
reviewed
Nov 14, 2024
sezna
approved these changes
Nov 14, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Big fan of QubitRef
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds some basic qubit live-ness tracking to the simulator, achieved by changing the
Value::Qubit
variant to a weak pointer to the qubit and having the execution environment own and track theRc
that owns the qubit. This provides a few benefits:Qubit<released>
when it is not, enabling easier debugging of qubit lifetimes.Of note, local perf testing showing no impact on performance (thanks, Rust zero-cost abstractions!), though it stands to reason this change could theoretically have some impact on programs that use many thousands of qubits.