| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
|
| |
|
|
|
|
|
|
|
| |
This involves making a temporary ErrorKind::TODO. That will continue
to exist until all errors (at least, the ones that make it out to
here) can be properly categorised.
Introducing this will let us work from the top and bottom towards the
middle.
|
| |
|
|
|
|
|
|
|
| |
This needs two kinds. We have decided to treat a non-shutdown
SpawnError as "unexplained" rather than as an InternalError.
There are many crates whose
From<futures::task::SpawnError> for Error
erroneously treat it as an internal error. We will fix them in a moment.
|
| |
|
|
|
| |
And change the comments to slightly reinterpret these errors, to
relate to the circumstances rather than error generation site.
|
| | |
|
| |
|
|
|
|
|
| |
This can be used in call sites where an error is thought not to be
possible.
The `source` will be used only for formatting messages.
|
| |
|
|
| |
This can contain a backtrace, which will be printed.
|
|
|
As per doc/Errors.md.
Currently there are no error kinds. Some will be added as we go along.
|