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
Upon determining the lack of convergence, the rt_poly_findroot function calls bu_log and returns -1 (indicating an error occurred). However, the only user of this function (rt_poly_roots) ignores the error. Should messages be printed to log if they are "not considered" errors?
If the contents of the log were free of non-error messages, then the log would be more helpful to users. Specifically, it would be nice if the default behavior was to only report to the log things that the user could do something about. Generally, having log categories such as SEVERE, ERROR, WARNING, DEVELOPER, etc. and letting API users configure the log would be most useful.
The text was updated successfully, but these errors were encountered:
Upon determining the lack of convergence, the rt_poly_findroot function calls bu_log and returns -1 (indicating an error occurred). However, the only user of this function (rt_poly_roots) ignores the error. Should messages be printed to log if they are "not considered" errors?
If the contents of the log were free of non-error messages, then the log would be more helpful to users. Specifically, it would be nice if the default behavior was to only report to the log things that the user could do something about. Generally, having log categories such as SEVERE, ERROR, WARNING, DEVELOPER, etc. and letting API users configure the log would be most useful.
The text was updated successfully, but these errors were encountered: