-
Notifications
You must be signed in to change notification settings - Fork 3
Try to guess element type from values in ilist.New #563
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
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified Files
|
|
| if not values: | ||
| elem_type = types.Any | ||
| else: | ||
| elem_type = values[0].type |
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.
this is not correct? the type should be union of all elements being used to construct the list.
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.
Oh, my bad. Thanks for fixing it!
CI is blocked by: * Requires kirin main * This kirin PR: QuEraComputing/kirin#563 * This kirin issue: QuEraComputing/kirin#564 Other than that, we should be good. I'm still targeting the kirin upgrade branch to make review easier, but this once the above issues are resolved, this can actually go into `main`. @weinbe58 please have a look at the address analysis, specifically at the `run_lattice` method. I had to change the signature a bit. --------- Co-authored-by: kaihsin <[email protected]>
This was removed as part of #344, so I'm not sure if it should be added back. However, without this change we always get
IList[AnyType]unless explicitly specifying the element type inilist.New. This breaks a bunch of tests (and code, really) in bloqade-circuit. Adding this back seemed like the much easier change than explicitly setting theelem_typeeverywhere.