Use msgspeck to serialize/deserialize tasks #320
Conversation
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
mak
force-pushed
the
feature/msgspec
branch
4 times, most recently
from
6f24303 to
eac1835
Compare
Member
|
Thanks, sounds like great idea. I'll check that soon. |
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.
msgspec claim to be fastest and smallest lib doing serialization, so why not try to use it -- free benefits are way more builtin types handled and other formats like msgpack
This is also a first step towards more static typing in tasks, ideally both
TaskandResourcesshould be a subclasses ofmsgspec.Structbut that is way more work than in can do right now ;]