-
Notifications
You must be signed in to change notification settings - Fork 97
Modernize NULL with nullptr in ll libraries and tests #5106
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
base: develop-linux
Are you sure you want to change the base?
Conversation
…lmeshoptimizer llphysicsextensionsos and test
31ec29d to
d51e9bc
Compare
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.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
|
I'm very conflicted about this change. On the one hand, modernization is a good thing. But big disruptive changes that are likely to conflict with a lot are just going to make it more difficult to to get this branch merged and shipped, and cause more integration pain downstream after the fact if we ever do get it shipped. I think the |
Description
Modernize NULL with nullptr in ll libraries and tests for increased type safety and compatibility with modern c++ library expectations that compare to nullptr_t but have no compatibility for NULL.
Related Issues
Issue Link: #5078
Checklist
Please ensure the following before requesting review:
Additional Notes