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
As you may have heard, there was some discussion last week about importing some of rust-encoding into Rust’s libstd or libextra. I think it is important to get the API right first (w.r.t. errors handling, incremental processing, etc.) The latest version of my proposal is on the rust-dev mailing list: (but see the rest of the thread.)
I would appreciate your feedback on this, especially on using conditions for error handling, and on the necessity for open-ended error handling as opposed to a fixed set of modes as in recent versions of the spec.
The text was updated successfully, but these errors were encountered:
Hi,
As you may have heard, there was some discussion last week about importing some of rust-encoding into Rust’s libstd or libextra. I think it is important to get the API right first (w.r.t. errors handling, incremental processing, etc.) The latest version of my proposal is on the rust-dev mailing list: (but see the rest of the thread.)
https://mail.mozilla.org/pipermail/rust-dev/2013-September/005556.html
I would appreciate your feedback on this, especially on using conditions for error handling, and on the necessity for open-ended error handling as opposed to a fixed set of modes as in recent versions of the spec.
The text was updated successfully, but these errors were encountered: