Skip to content

Responding to Serialization Errors #257

@mitsuhiko

Description

@mitsuhiko

Due to bincode-org/bincode#245, bincode-org/bincode#167 and a few others it's not uncommon that one can end up in a situation where objects fail to serialize.

It would be nice to be able to be able to respond to these errors in a way that lets you still send something into the channel so that the receiver can deal with the errors.

I tried using the channel a second time after send() which seems to work because the bincode serialization fails internally when filling the buffer, before actually sending but I believe something corrupts internally which seem to cause errors like this: Io(Custom { kind: NotFound, error: "Bogus destination port." })

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions