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
Copy file name to clipboardExpand all lines: text/0000-project-error-handling.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -20,8 +20,8 @@ The error handling project group aims to reduce confusion on how to structure er
20
20
21
21
### Agree on and define common error handling terminology
22
22
23
-
- Recoverable error: An error that can reasonably be expected to be encountered e.g. a missing file.
24
-
- Unrecoverable error: An error that cannot reasonably be expected to happen and which indicates a bug e.g. indexing out of bounds.
23
+
- Recoverable error: An error that can be reacted and recovered from when encountered e.g. a missing file.
24
+
- Unrecoverable error: An error that cannot reasonably be reacted to or recovered from and which indicates a bug e.g. indexing out of bounds.
25
25
- Error Type: A type that represents a recoverable error. Error types can optionally implement the `Error` trait so that it can be reported to the user or be converted into a trait object.
26
26
- Reporting Type: A type that can store all recoverable errors an application may need to propagate and print them as error reports.
27
27
- Reporting types can represent the recoverable errors either via concrete types, likely parameterized, or trait objects.
@@ -118,7 +118,7 @@ The project group will create RFCs for various changes to the standard library a
118
118
119
119
### Who are the initial shepherds/leaders? (This is preferably 2–3 individuals, but not required.)
120
120
121
-
Jane Lusby, Andrew Gallant, and Sean Chen.
121
+
Jane Lusby(@yaahc_), Andrew Gallant(@BurntSushi), and Sean Chen(@seanchen1991).
0 commit comments