Add backwards compatibility to qml.generator()
#2304
Closed
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.
Context:
In previous versions of PennyLane,
Operator.generator
was a property, that returned a list of the form[type, float]
or[array, float]
.In the current master, this has been changed.
Operator.generator
is now a method, and it returns an Operator instance.In Add
qml.generator(op)
function #2256, a high-levelqml.generator()
function was added, intended to be the user-facing interface toOperator.generator()
.Description of the Change: A small modification to
qml.generator()
has been made, to ensure it continues to work with old-style operators that define theOperator.generator
property. In addition, a deprecation warning is raised.Benefits:
qml.generator()
should work with old-style operators.Possible Drawbacks: This backwards compatibility is constrained, in that it requires developers start using
qml.generator
, a new function!Related GitHub Issues: n/a