feat: re-export Receiver error types (#488) - #489
Merged
Conversation
`Receiver` was re-exported but its error types were not, so a caller that wanted to name `RecvError` -- to write `impl From<RecvError>` for its own error type, for example -- had to add `flume` as a direct dependency. Re-export the three receiver-side error types. The `Send*` errors are left out because `Sender` is internal to the daemon and never handed to callers. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Luni-4
approved these changes
Aug 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #488
Problem:
Receiverwas re-exported but its error types were not, so a caller that wanted to nameRecvError-- to writeimpl From<RecvError>for its own error type, for example -- had to addflumeas a direct dependency.Fix:
Re-export the three receiver-side error types.