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
We have quite a lot of @debug statements floating around the code base, and I wonder how much additional value a lot of them provide. Debug messages like @debug "run model..." in a function called runmodel really don't provide any additional information over and above what a stack trace already provides, while cluttering the code.
I would be keen to understand whether
anyone feels that these debug messages provide value over and above what we get for free from stack traces and
there would be any objections to removing a lot of the debug messages.
The text was updated successfully, but these errors were encountered:
@willtebbutt That's a good point - many of these codes are written when Julia's debugging environment is less mature. Indeed, some @debug messages are a bit redundant and can be safely removed.
We have quite a lot of
@debug
statements floating around the code base, and I wonder how much additional value a lot of them provide. Debug messages like@debug "run model..."
in a function calledrunmodel
really don't provide any additional information over and above what a stack trace already provides, while cluttering the code.I would be keen to understand whether
The text was updated successfully, but these errors were encountered: