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
Some functions (especially simple getter-like functions) could probably avoid returning a Result and simply return the type, because we don't actually expect exceptions to be thrown on the C++ side.
As well, reconsider ErrorCode. Perhaps a String is sufficient for these cases and we can avoid the enum altogether.
The text was updated successfully, but these errors were encountered:
147: implement std::error::Error for ErrorCode r=grovesNL a=bootra-dev
With respect to #49, I think that keeping an error type is the most flexible way to handle errors. This pull request implements Error (and by requirement, Display), to make integrating with other error types easier.
Co-authored-by: bootra-dev <[email protected]>
Some functions (especially simple getter-like functions) could probably avoid returning a
Result
and simply return the type, because we don't actually expect exceptions to be thrown on the C++ side.As well, reconsider
ErrorCode
. Perhaps aString
is sufficient for these cases and we can avoid the enum altogether.The text was updated successfully, but these errors were encountered: