| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
Since there is currently only one error type that can occur when
encoding, it doesn't make sense to use the full Error type here.
This split will help us downstream, as we no longer need to
categorize tor_bytes::Error as "an error in encoding or decoding".
I considered renaming Error to DecodeError, but that had pretty huge
downstream effects, and didn't seem to be worth it.
|
| |
|
|
|
| |
Also note an issue with the design of tor-bytes::Error that should
probably go in a separate MR.
|
| |
|
|
| |
Writing is going to be able to give errors too.
|
| |
|
|
| |
Including supporting machinery, new kind field, etc.
|
| |
|
|
|
|
| |
This crate's Error type is too low-level to have an ErrorKind, but
it does make sense to use InternalError for the internal errors
here.
|
|
|
This will cause some pain for now, but now is really the best time
to do this kind of thing.
|
