-
Notifications
You must be signed in to change notification settings - Fork 184
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
Handling empty lists passed to Python kernels #1438
Conversation
Command Bot: Processing... |
1 similar comment
Command Bot: Processing... |
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Signed-off-by: Alex McCaskey <amccaskey@nvidia.com>
Signed-off-by: Alex McCaskey <amccaskey@nvidia.com>
Signed-off-by: Alex McCaskey <amccaskey@nvidia.com>
Signed-off-by: Alex McCaskey <amccaskey@nvidia.com>
Signed-off-by: Alex McCaskey <amccaskey@nvidia.com>
Command Bot: Processing... |
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.
👍
Command Bot: Processing... |
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Inject the kernel
FuncOp
when packing input runtime arguments into the opaque arg used byaltLaunchKernel
. This provides better handling of runtime argument types via the LLVM TypeSwitch utility.Without this we should experience issues with regards to processing empty lists passed as runtime arguments. Currently we can only know that the argument is a
list
and infer the element type by checking the type of the list's first element, which does not exist if the list is empty. This PR brings the kernel argument signature to this processing step, and so we can check / process the args knowing the required argument type.