-
Notifications
You must be signed in to change notification settings - Fork 236
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 #51
Comments
Sure, thanks. Given that this project is not under very active development, and IMHO it's more of a cosmetic / stylistic issue, I guess this is low priority. Please consider providing a PR. |
How do you think about to use a development tool like “clang-tidy” for corresponding source code adjustments? |
In general, a great tool. For current projects I also love clang-format. But again, since this is not really active, I think we won't be able to invest the time to properly set up these tools for this project. Lack of proper testing makes this all the more difficult. A wider systematic reformatting or cleanup would also mean other branches are existing small extensions that we and maybe others have locally would need to be updated to be able to merge the occasional bugfix that is applied to master here in the future. I would consider merging PRs that make isolated and very-easy-to-verify cleanups, but maybe not major refactoring across the whole code base. However, I personally think its not really worth to invest too much time here at this stage. Are you planning major development on top of the current code base? Maybe you might better off forking the project and taking over maintenance yourself there in the way you like, sorry. |
I am generally checking the change acceptance in some software areas (before I might contribute further improvements). |
Ok, that is very reasonable. Sorry this project isn't more active and thus the answer is rather negative. |
Extra null pointer checks are not needed in functions like the following.
The text was updated successfully, but these errors were encountered: