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
My understanding is that assert statements can be removed at compile time (to improve performance, which seems specifically relevant to Graphium), so any error that a downstream user can make and should be informed about should ideally be a raised and specific (e.g. RuntimeError, ValueError, TypeError, KeyError, ...) Exception. To have sanity checks during debugging / development, you can still use assert statements.
My understanding is that assert statements can be removed at compile time (to improve performance, which seems specifically relevant to Graphium), so any error that a downstream user can make and should be informed about should ideally be a raised and specific (e.g. RuntimeError, ValueError, TypeError, KeyError, ...) Exception. To have sanity checks during debugging / development, you can still use assert statements.
Originally posted by @cwognum in #414 (comment)
The text was updated successfully, but these errors were encountered: