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
Looking at my own library uses, there is one more thing I'd like to see before releasing a 0.3 version: better errors.
Right now, all parse errors and all I/O errors return the same information. This means doing smart error handling besides "just return it to the caller" is not easy, and printing out error information is not very useful. If there is an I/O error reading from the file, for instance, we have no way to give useful information about it back.
Looking at my own library uses, there is one more thing I'd like to see before releasing a 0.3 version: better errors.
Right now, all parse errors and all I/O errors return the same information. This means doing smart error handling besides "just return it to the caller" is not easy, and printing out error information is not very useful. If there is an I/O error reading from the file, for instance, we have no way to give useful information about it back.
I would also make sure that we are following the error handling guidelines for the future of Rust.
The text was updated successfully, but these errors were encountered: