-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Ensure TemplateOptimization
returns native-symbolic objects
#11107
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8 changes: 8 additions & 0 deletions
8
releasenotes/notes/template-match-symbols-c00786155f101e39.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
--- | ||
fixes: | ||
- | | ||
The :class:`.TemplateOptimization` pass will now return parametric expressions using the native | ||
symbolic expression format of :class:`.ParameterExpression`, rather than always using Sympy. | ||
For most supported platforms, this means that the expressions will be Symengine objects. | ||
Previously, the pass could return mismatched objects, which could lead to later failures in | ||
parameter-handling code. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
Technically this is a bit of a larger change than completely required, but I was having a hard time parsing what was going on with several objects having multiple possible types, being created long before being initialised, and
try/except
early returns.Strictly there's a minor (positive) behavioural change here: previously, the
try/except
handling would cause matches that had multiple possible solutions to fail binding, whereas now it'll pick one of the solutions. This makes the pass strictly more powerful, since templates are isolated from each other based on maximal matching, but in practice, multiple solutions require non-linear parametrised circuits, and there aren't any of those in the template library.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.
Does it make sense to doc the potential behavioural change in an upgrade release note?
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.
I think I prefer not adding a release note, because I'd prefer to not commit the API to supporting arbitrarily complex symbolic solutions; we may very well want to replace this handling with simple in-house symbolic linear solvers in the future if we want to extend this to supporting runtime classical parameters.
Let me mark this for merge now to shorten the dependency chain, and if we decide differently, we can revisit.