Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

tricky-pipe: consider propagating deserialization errors to the receiver #32

Open
hawkw opened this issue Nov 22, 2023 · 0 comments
Open

tricky-pipe: consider propagating deserialization errors to the receiver #32

hawkw opened this issue Nov 22, 2023 · 0 comments

Comments

@hawkw
Copy link
Contributor

hawkw commented Nov 22, 2023

i initially proposed this in #29:

also, it would be nice if an attempt to send a message through a DeserSender that results in a deserialize error also sent the deserialize error to the receiver, as well as returning it to the sender...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hawkw