| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
This commit deprecates the `EncodeError::always_bug` function with a
`From<EncodeError> for Bug` trait, which is a more semantically correct
way to perform this action.
|
| |
|
|
|
|
|
|
|
|
| |
Actually, to avoid making a breaking change, I'm deprecating
BadMessage and creating a new InvalidMessage variant that takes a
Cow. This way I don't need to track every crate that re-exposes
tor_bytes::Error and call this a breaking change in those.
Making this change will allow tor_bytes errors to be much more
helpful.
|
| | |
|
| |
|
|
| |
This will help down the line as we make more writers fallible.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
