-
Notifications
You must be signed in to change notification settings - Fork 454
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
[BUG] Completion of error handling #1496
Comments
No. We dont check results of *allocs. Just let the program crash if they fail. |
BTW what static checker are you using? |
💭 I hope that you would like to avoid undefined behaviour. |
In modern system, malloc should almost never fail because swap exists. One exception is programming bug such as |
💭 Some software users tend to prefer defined behaviour. Some functions are known where return values can be overlooked. |
Modern compilers are already smart enough to detect some UBs. We also use ASAN and UBSAN. I think it's enough for me. |
🔮 How will chances evolve to benefit any more also from the means of aspect-oriented software development? |
Would you like to add more error handling for return values from functions like the following?
The text was updated successfully, but these errors were encountered: