-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Revert memory-owning expr.Var
nodes
#11667
Conversation
One or more of the the following people are requested to review this:
|
Ach, I've borked this pretty badly and need to redo it, possibly by avoiding |
This commit is a roll-up reversion of the following commits (PR): * commit a79e879 (Qiskit#10977) * commit ba161e9 (Qiskit#10974) * commit 50e8137 (Qiskit#10944) This is being done to clear the 1.0 branch of memory-owning `expr.Var` variables and `Store` instructions. It should be re-applied once 1.0 is released. This wasn't done by individual `revert` operations, because there were also significant structural changes introduced in those PRs that were very valid and should be maintained. Cross-references to `Var` nodes from other functions have been removed for now. Making `Var` and `types.Type` hashable is maintained, as is the `Var.standalone` function, in order to prepare the ground for the inclusion of proper `Var` nodes in a minor release.
33ba003
to
cfb317e
Compare
Ok, I redid the reversion much more manually, and this should be rather better now. |
Pull Request Test Coverage Report for Build 7700797447
💛 - Coveralls |
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.
Given the time frame for 1.0.0 I agree reverting this before the release is probably the right call at this point. We should revert this after we tag 1.0.0rc1 and development for 1.1.0 open up on main
.
This reverts commit 052d889.
Summary
This commit is a roll-up reversion of the following commits (PR):
QuantumCircuit.append
validates captures in control-flow #10974)Var
nodes #10944)This is being done to clear the 1.0 branch of memory-owning
expr.Var
variables andStore
instructions. It should be re-applied once 1.0 is released.This wasn't done by individual
revert
operations, because there were also significant structural changes introduced in those PRs that were very valid and should be maintained. Cross-references toVar
nodes from other functions have been removed for now.Making
Var
andtypes.Type
hashable is maintained, as is theVar.standalone
function, in order to prepare the ground for the inclusion of properVar
nodes in a minor release.Details and comments