Update gradient logic for Qiskit Rust circuit data implementation (backport #188) #198
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.
Summary
Fixes #181
This updates internals of the gradients which more directly manipulated circuit data the way it was when it was managed in Python. The Rust implementation is changing things to be more performant but things are also different so this changes the logic to try accommodate as things are currently done, which is what is in Qiskit stable releases at present, and the new Rust implementation which is presently in main branch of Qsikit repo. #181 notes the aspect of CI which is failing is when we test against main which was done to monitor for any problems here due to changes.
This has partially fixed things but there is another aspect, that I failed to notice/note in #181 that also occurs
which has not been addressed at present.
Details and comments
This is an automatic backport of pull request #188 done by [Mergify](https://mergify.com).