-
Notifications
You must be signed in to change notification settings - Fork 103
cleanup(storage)!: ranged reads made type-safe #2924
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cleanup(storage)!: ranged reads made type-safe #2924
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2924 +/- ##
==========================================
+ Coverage 96.17% 96.19% +0.01%
==========================================
Files 105 105
Lines 4394 4411 +17
==========================================
+ Hits 4226 4243 +17
Misses 168 168 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Specify ranged reads using a safe type, which does not permit invalid ranges (such as negative length limits). No need to have a `ReadError` if the request is well-defined by construction.
fe01211 to
086e388
Compare
dbolduc
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but there might be a bug predating this PR for the tail case
Specify ranged reads using a safe type, which does not permit invalid
ranges (such as negative length limits). No need to have a
ReadErrorif the request is well-defined by construction.
Fixes #2849