Implement serialization and deserialization for file dict #2
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.
Doing the large-pr in acryldata flow, but in your personal branch.
I opted to make serializer and deserializer required arguments, because adding defaults as json.dumps and json.loads respectively would add extra overhead for basic
FileBackedDict[str]
orFileBackedDict[int]
objects, when the identify function would be sufficient. I don't think it's too onerous to have to specify your serializer and deserializer, even if it's just the identity function or json functions, and in general something the user should be thinking about when they're usingFileBackedDict
Checklist