-
Type: Task
-
Resolution: Unresolved
-
Priority: Unknown
-
Affects Version/s: None
-
Component/s: None
-
None
Our BSON library currently has several different specific Error and Result types for the various modules and types we have. This can be quite inconvenient when writing a new method that returns a Result, as new error types need to be introduced when the existing ones don't match up with the specific case. When we do our next release with breaking changes, we should introduce general-purpose Error and Result types, similar to what already exists within the driver, and model the current errors we have under a unified enum within the new Error type.
- related to
-
RUST-347 Consider consolidating BSON error types
- Closed