-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Removal of _index
and _registers
from Bit
#11596
Removal of _index
and _registers
from Bit
#11596
Conversation
Pull Request Test Coverage Report for Build 7700646687
💛 - Coveralls |
One or more of the the following people are requested to review this:
|
_index
and _registers
from Bit
@mtreinish The effects of this PR in QPY.. are breaking the QPY specification? If so, we could delay this to 2.0 or to increase the QPY version. |
There shouldn't be an issue for qpy here. The one place this will come up is probably in how we query the index and register in the serialization side. But if we're doing that we should be able to move to |
I'll be taking over these efforts from now on since this PR would be helpful for #13269. |
26834dd
to
7f8cb05
Compare
Possible close this one as pointless now, since performance looks much better nowadays. |
Due to recent discussions and a change of perspective, we have decided to no longer pursue this approach. The PR is now closed! 🔨 |
[sad] Sebastian Brandhofer reacted to your message:
…________________________________
From: Raynel Sanchez ***@***.***>
Sent: Thursday, February 13, 2025 5:58:33 PM
To: Qiskit/qiskit ***@***.***>
Cc: Sebastian Brandhofer ***@***.***>; Author ***@***.***>
Subject: [EXTERNAL] Re: [Qiskit/qiskit] Removal of `_index` and `_registers` from `Bit` (PR #11596)
Due to recent discussions and a change of perspective, we have decided to no longer pursue this approach. The PR is now closed! 🔨 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored
Due to recent discussions and a change of perspective, we have decided to no longer pursue this approach. The PR is now closed! 🔨
—
Reply to this email directly, view it on GitHub<#11596 (comment) >, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BDMWA4FIYCEYW3G4NCTQNAD2PTMMTAVCNFSM6AAAAABCBC5DHOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXGM2TEMRSHE >.
You are receiving this because you authored the thread.Message ID: ***@***.***>
[raynelfss]raynelfss left a comment (Qiskit/qiskit#11596)<#11596 (comment) >
Due to recent discussions and a change of perspective, we have decided to no longer pursue this approach. The PR is now closed! 🔨
—
Reply to this email directly, view it on GitHub<#11596 (comment) >, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BDMWA4FIYCEYW3G4NCTQNAD2PTMMTAVCNFSM6AAAAABCBC5DHOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXGM2TEMRSHE >.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Summary
Addresses and builds on top of #11407
Details and comments
With the removal of
_index
and_registers
fromBit
,Bit
s become opaque and can only be distinguished by theirid
. This breaks several test cases, requires a new de/serialization and a caching ofControlledGate.definition
. These issues are addressed in this PR, leaving a potential refactoring ofLayout
for the future (see #11604).