-
Notifications
You must be signed in to change notification settings - Fork 634
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
Deprecate Operator.expand
function
#5994
Conversation
Hello. You may have forgotten to update the changelog!
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5994 +/- ##
==========================================
+ Coverage 99.59% 99.65% +0.05%
==========================================
Files 427 427
Lines 41719 40745 -974
==========================================
- Hits 41551 40605 -946
+ Misses 168 140 -28 ☔ View full report in Codecov by Sentry. |
Co-authored-by: Thomas R. Bromley <[email protected]>
Co-authored-by: Mudit Pandey <[email protected]>
Co-authored-by: Mudit Pandey <[email protected]>
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.
👍
`Operator.expand` is deprecated (PennyLaneAI/pennylane#5994). `Operator.decomposition` should be used instead. --------- Co-authored-by: ringo-but-quantum <[email protected]> Co-authored-by: Ali Asadi <[email protected]>
`Operator.expand` is deprecated (PennyLaneAI/pennylane#5994). `Operator.decomposition` should be used instead. --------- Co-authored-by: ringo-but-quantum <[email protected]> Co-authored-by: Ali Asadi <[email protected]>
Deprecated since it is redundant bloat and can be done manually pretty easily.
[sc-65069]