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
A place to discuss the usage of a result type, option type or exceptions in oml.
From #153@struktured wrote
I think adopting a result or or_error type is interesting if done appropriately. For the most part I would definitely go beyond optional if you are going to bother at all encoding the errors in return types.
The strictness and explicitness of the error handling should correspond to how much we would expect a particular function to "misbehave", and thus will probably need to vary by module and/or function signature. In general it's probably best to prefer implicit error handling so mathematicians can focus on the meat of their computations, but I'm open to counter arguments.
For instance, it would be nice to know when training a model that some particular hyperparameter was invalid or led to non-convergence- we can then condition on it that information and try different inputs. More generally, you could imagine any function reporting what input parameter or derived value (with semantically meaningful name) broke the results.
The text was updated successfully, but these errors were encountered:
A place to discuss the usage of a result type, option type or exceptions in oml.
From #153 @struktured wrote
The text was updated successfully, but these errors were encountered: