You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to add some error handling here, if that suits you.
How would you like errors of this nature to be handled?
I am happy to just print error and exit the program (probably something stronger than an assert - as asserts can be compiled out).
The text was updated successfully, but these errors were encountered:
There is an ettor handling mechanism, you can see it used in primops.c a lot. The macros used for error handling are in assertions.h. They allocate themselves though so maybe better to exit, like you say.
Looking at the implementation for
obj_new
we seea call to
malloc
can failI would like to add some error handling here, if that suits you.
How would you like errors of this nature to be handled?
I am happy to just print error and exit the program (probably something stronger than an assert - as asserts can be compiled out).
The text was updated successfully, but these errors were encountered: