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
Right now, the only way I see for a program calling the UnQLite wrapper to know the nature of an error is to compare the error string associated with the error with the string literals in UnQLite's error.rs. This seems unsafe.
The Custom struct that is returned for the error contains UnQLite's numeric error code and the ErrorKind enum variant that the wrapper assigned to it. However, even though the ErrorKind enum is public, the fields of the UnQLite struct are private and there is no way for the calling program to access this.
Please add methods to access the fields of a Custom struct:
Right now, the only way I see for a program calling the UnQLite wrapper to know the nature of an error is to compare the error string associated with the error with the string literals in UnQLite's error.rs. This seems unsafe.
The
Custom
struct that is returned for the error contains UnQLite's numeric error code and the ErrorKind enum variant that the wrapper assigned to it. However, even though theErrorKind
enum is public, the fields of theUnQLite
struct are private and there is no way for the calling program to access this.Please add methods to access the fields of a
Custom
struct:The text was updated successfully, but these errors were encountered: