-
Notifications
You must be signed in to change notification settings - Fork 3
Fix bug caused by type check fix (bloqade-circuit#566) #542
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
Conversation
|
Oops. Just look at the one commit I made. Rebasing now. |
1c3115c to
b7cb784
Compare
|
Rebase to main done. |
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified Files
|
|
Satisfying the coverage check will take a bit for me to manually construct an IfElse object from blocks not regions. |
|
I think we should have some simple test that captures this bug apparently it was not captured by current unit tests. |
|
Note that most of the if-else tests are marked xfail due to the recent restriction of no early return statements in scf. |
|
Please review and merge once CI passes. |
|
After backporting to 0.17: |
|
@Roger-luo should we think about adding downstream testing? That would have also caught this bug. |
weinbe58
left a comment
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
Fixes [bloqade-circuit/issues/566](QuEraComputing/bloqade-circuit#566)
Fixes bloqade-circuit/issues/566