-
Notifications
You must be signed in to change notification settings - Fork 59
Clarification in sharp bits page for qml.allocate behaviour
#2317
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
base: v0.14.0-rc
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2317 +/- ##
==========================================
- Coverage 97.27% 97.27% -0.01%
==========================================
Files 107 107
Lines 12952 12950 -2
Branches 1077 1077
==========================================
- Hits 12599 12597 -2
Misses 290 290
Partials 63 63 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| initial ones from ``qml.device``. If the pool of wires from ``device`` is | ||
| called "device" and the pool of wires from ``qml.allocate`` is called | ||
| "dynamic", future calls to ``qml.allocate`` can reuse wires from the | ||
| dynamic pool, but not from the device pool. |
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.
nice 👍
Co-authored-by: David Ittah <[email protected]>
| * A clarification was made in the :doc:`Sharp Bits page <../dev/sharp_bits>` for the behaviour of | ||
| :func:`qml.allocate <~.allocate>` when used with Catalyst. | ||
| [(#2317)](https://github.com/PennyLaneAI/catalyst/pull/2317) | ||
|
|
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.
Needs to be moved to v0.14 changelog
Context: The copy in the sharp bits page for
qml.allocate's differences from PL doesn't quite illustrate the behaviour properly.Description of the Change: Adds clarification
Benefits: Clarity
Possible Drawbacks:
Related GitHub Issues: