You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As pointed out in this comment and this comment, it will be easier to maintain and modify share encoding code if we also have a canonical API for calculating the number bytes and shares that compact and sparse share use. There are many different uses of this estimation logic, so getting a perfect API or modifying the existing code to use such an API could take a few PRs. We should track them here.
The text was updated successfully, but these errors were encountered:
I don't see an immediate need for a separate API that returns number of bytes but it would be easy to implement (number of shares needed * share size) so proposal to mark this as resolved for now? @evan-forbes
As pointed out in this comment and this comment, it will be easier to maintain and modify share encoding code if we also have a canonical API for calculating the number bytes and shares that compact and sparse share use. There are many different uses of this estimation logic, so getting a perfect API or modifying the existing code to use such an API could take a few PRs. We should track them here.
The text was updated successfully, but these errors were encountered: