Non-effectful serialization and deserialization #1380
Draft
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.
This is an exploration of #853.
Serializers cannot fail, like in zio-json. Deserialization is no longer allowed to be side-effectful, so serializers like the Confluent Avro serde (which communicates with a schema registry) will have to be run in the user's own code. We should add an example to the documentation.
I thought a free error type for the deserialization error would be nice, but at some point it has to be integrated with other errors in the Runloop, which means wrapping it in an exception for now. Needs something better..