Functionality for Reed-Solomon object encoding #3429
Closed
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.
currently, i'm trying to implement single-level encoding. It's simpler and less resource intensive. Plus it's within current multi-level slicing restrictions like 60faa73 (smth else?)
an obvious alternative would be a two-level format, where the resulting objects of slicing by length (up to MaxObjectSize) are wrapped into new objects due to the recursive structure. I haven't found any advantages in it yet