errors
errors copied to clipboard
pingcap
Simple error handling primitives
While I understand the desire to not re-implement `WithStack()`, by wrapping it in `AddStack()` the `AddStack()` function appears on the stack trace, unlike `WithStack()` which does not because `callers()` aliases...
Current `Error()` method will print the log message first then with the error rfc code, it may be better to print the error rfc code in front of log message....
- Add `Warp` and `Cause` interface to save cause error. - Add `FastGenWithCause` to generate error with error code and cause error
TiDB use same error code to represent a class of code, like `8200` contain a series of error related to unsupported ddl. When using this terror lib, TiDB will panic....
our upstream have change a lot, go1.12 introduce new stack frame we should follow up them.
raises go version to 1.18 this is a breaking change since consumers will update with `errors.RedactLogEnabled.Store(&errors.RedactLogEnable)`. ideally this wouldn't be exposed & instead there'd be a function `errors.SetRedactLogEnabled(...)` & even...
Give an tree of errors: ``` A + B - C | + D - E ``` For now `WalkDeep` walks `A` and `multierr(B-C, D-E)` and then returns. It isn't...
