Expand description
One error type for both transports.
The implementations have their own — ytsaurus_client::Error carries HTTP
status codes, ytsaurus_rpc::Error carries a nested TError — and neither
belongs in an interface the other implements. This keeps what a caller can
actually act on and carries the original underneath, so nothing is lost.
Modules§
- codes
- Error codes both transports report, for callers that match on them.
Enums§
- Error
- A failure from either transport.
Functions§
- describe
- Renders a chain of sources, which is where the transport’s own detail lives.
Type Aliases§
- Result
- The interface’s result type.