-
Notifications
You must be signed in to change notification settings - Fork 215
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
Improve error message when assigning real valued arrray with complex numbers #2341
Comments
Not really. This is exactly the same error message, just being rendered from the GPU. If you do what the error message suggests, running with
The only thing different here is that this is rendered as a plain Exception, which isn't easy to fix, and the fact that every thread reports an exception, which has already been reported in #1780. So I think we can close that in favour of the existing issue. |
And FWIW, it's not possible to detect and special case this before launching a GPU kernel, because the InexactError depends on the actual data:
|
I did the hard thing and improved reporting in #2342 |
Cool thanks! |
Hi,
I noticed a very long and cryptic error message when I assign a Float32 array accidentally with an ComplexF32 value.
Is there a way to improve this?
The text was updated successfully, but these errors were encountered: