Developer day outcome:
Define more explicit and consistent error types and handling
Trying to capture some of the current frustrations:
- Error types can be lossy, losing a necessary provenance of why and where the error arose.
- Errors often get collapsed into NAs without a clear rational communicated to the user
- (new given redesign): Errors must be able to be serialized-to- and deserialized-from- dcf files (PACKAGES)
Developer day outcome:
Define more explicit and consistent error types and handling
Trying to capture some of the current frustrations: