-
Notifications
You must be signed in to change notification settings - Fork 172
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
ERANGE usage #201
Comments
I see that the METAL_XYZ return codes are used for routines that return unsigned values and EINVAL and ERANGE are used for routines that return int. Has the possible case been ruled out for the unsigned routines that the error code and valid data would overlap and the user would think the routine was not successful? |
Please could you provide some concrete examples to illustrate your point? |
This issue has been marked as a stale issue because it has been open (more than) 45 days with no activity. |
@tammyleino: I tried to find the code you mentioned without success. As it is an old issue, perhaps it is no longer valid. Could you point me to the issue? Otherwise, I will close the issue. |
@arnopo It looks like an outdated issue. You can close it. |
Is there a reason a new error code, METAL_ERANGE, was not created instead of using -ERANGE?
The text was updated successfully, but these errors were encountered: