Skip to content
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

Remove unnecessary null pointer checks #6

Closed
elfring opened this issue Jul 27, 2016 · 13 comments
Closed

Remove unnecessary null pointer checks #6

elfring opened this issue Jul 27, 2016 · 13 comments

Comments

@elfring
Copy link

elfring commented Jul 27, 2016

An extra null pointer check is not needed in functions like the following.

@amooty
Copy link

amooty commented Aug 2, 2016

Filed as internal issue #135159.

@superfunc
Copy link
Contributor

superfunc commented Jan 28, 2018

@elfring
Copy link
Author

elfring commented Jan 28, 2018

There are further update candidates to consider, aren't there?

@superfunc
Copy link
Contributor

Looks like I was wrong; I hadn't realized this was pointing to a more general problem and not those specific callouts, my apologies.

@elfring
Copy link
Author

elfring commented Jan 28, 2018

I am just curious if all possible improvements were integrated into this software for the reported search pattern.

@elfring
Copy link
Author

elfring commented Jan 28, 2018

@elfring
Copy link
Author

elfring commented Jan 28, 2018

How will the software evolution be continued around a class like “GlfUVTextureStorageData”?

@elfring
Copy link
Author

elfring commented Jun 25, 2018

@Cewein
Copy link

Cewein commented Dec 26, 2024

This issue is quite old, is it still relevent ? I am willing to do a thorough check if needed.

@meshula
Copy link
Member

meshula commented Dec 27, 2024

Bug reports with repro's, and PRs with code quality or quality of life improvements are always welcome of course.

I don't think it's useful to keep a general issue open for years as a substitute for an ongoing review process though. OpenUSD is subject to extensive testing, as well as continuous development, so I'd suggest that if you do undertake a check, please open PRs with suggested improvements, or issues with bug reports if it's not clear how to proceed.

@meshula
Copy link
Member

meshula commented Dec 27, 2024

I'm closing it out, per my explanation above.

@meshula meshula closed this as completed Dec 27, 2024
@elfring
Copy link
Author

elfring commented Dec 27, 2024

🔮 Would you like to share any more information also according to an internal issue like #135159?

@meshula
Copy link
Member

meshula commented Dec 27, 2024

135159 is our internal tracking number for this github issue. There is no extra information there.

The pattern of checking the glProgram does not impact correctness or performance so it will probably not get attention in a reasonable amount of time. Since you are still interested in this issue would mind perhaps working with @Cewein to create a PR for us to look at, since he has offered to help?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants