-
Notifications
You must be signed in to change notification settings - Fork 320
Guard against user defined major and minor macros
#7074
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
|
Uuuh, I don't know whether this is a good idea, we could end up adding more and more of these macros. And I don't think it will fix the problem, because then if the user wants to use |
|
The other option would be to change the member function to @pciolkosz what do you prefer? |
This comment has been minimized.
This comment has been minimized.
This API is already released, we cannot change that. I really think that this is user's problem, because if you have a look for example at It's not that I don't want to help the user, but this solution is not sustainable. We are already trying our best to prevent the user to modify our internals, but I don't think we should do that for everything. |
|
@davebayer @miscco the "user" in this situation is just one of the CUDA samples, specifically: That said, I don't see any macro definition of |
|
Yeah I am really wondering how this could happen, but that the error in question is: This clearly hints at |
|
I've done some research and those macros come from |
Addresses nvbug5781562
def970f to
85ad12c
Compare
|
closing in favor of #7099 |
😬 CI Workflow Results🟥 Finished in 6h 00m: Pass: 95%/91 | Total: 2d 20h | Max: 6h 00m | Hits: 71%/201726See results here. |
We need to avoid using those identifiers as they are frequently used by users
Addresses nvbug5781562