-
Notifications
You must be signed in to change notification settings - Fork 603
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
Remove decomp_depth
from qml.device
constructor
#6234
Conversation
…pennylane into remove-decomp-depth
Co-authored-by: Astral Cai <astral.cai@xanadu.ai>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6234 +/- ##
==========================================
+ Coverage 99.58% 99.59% +0.01%
==========================================
Files 443 444 +1
Lines 42273 42336 +63
==========================================
+ Hits 42096 42163 +67
+ Misses 177 173 -4 ☔ View full report in Codecov by Sentry. |
…o remove-decomp-depth
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.
Small change needed for rendering docs correctly, otherwise looks good.
The `decomp_depth` keyword argument only served to prevent operations from being fully decomposed to the target gateset. It is now removed. [sc-72706] --------- Co-authored-by: Astral Cai <astral.cai@xanadu.ai> Co-authored-by: Mudit Pandey <mudit.pandey@xanadu.ai>
The `decomp_depth` keyword argument only served to prevent operations from being fully decomposed to the target gateset. It is now removed. [sc-72706] --------- Co-authored-by: Astral Cai <astral.cai@xanadu.ai> Co-authored-by: Mudit Pandey <mudit.pandey@xanadu.ai>
The
decomp_depth
keyword argument only served to prevent operations from being fully decomposed to the target gateset. It is now removed.[sc-72706]