-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Fix typing error in random_circuit
conditionals
#9651
Fix typing error in random_circuit
conditionals
#9651
Conversation
The `condition` field is expected to be a comparison of a register or bit with a Python bigint (or bool, which is a subclass). This function could previously output fixed-width Numpy types, however, which could cause problems with subsequent bitmasks if the constructed masker/maskee _was_ a Python bigint and couldn't fit in the Numpy type. The more recent `IfElseOp` enforces the correct typing, it's just the old form that doesn't.
Thank you for opening a new pull request. Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone. One or more of the the following people are requested to review this:
|
Pull Request Test Coverage Report for Build 4264841870
💛 - Coveralls |
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.
LGTM!
LGTM |
The `condition` field is expected to be a comparison of a register or bit with a Python bigint (or bool, which is a subclass). This function could previously output fixed-width Numpy types, however, which could cause problems with subsequent bitmasks if the constructed masker/maskee _was_ a Python bigint and couldn't fit in the Numpy type. The more recent `IfElseOp` enforces the correct typing, it's just the old form that doesn't. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 94e9480)
The `condition` field is expected to be a comparison of a register or bit with a Python bigint (or bool, which is a subclass). This function could previously output fixed-width Numpy types, however, which could cause problems with subsequent bitmasks if the constructed masker/maskee _was_ a Python bigint and couldn't fit in the Numpy type. The more recent `IfElseOp` enforces the correct typing, it's just the old form that doesn't. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 94e9480) Co-authored-by: Jake Lishman <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Summary
The
condition
field is expected to be a comparison of a register or bit with a Python bigint (or bool, which is a subclass). This function could previously output fixed-width Numpy types, however, which could cause problems with subsequent bitmasks if the constructed masker/maskee was a Python bigint and couldn't fit in the Numpy type. The more recentIfElseOp
enforces the correct typing, it's just the old form that doesn't.Details and comments
Fix #9649