Derive sliced payload size from ReaderSeeker
#545
Labels
enhancement
Improving existing functionality
I3
Minimal impact
performance
More of something per second
S4
Routine
U4
Nothing urgent
Is your feature request related to a problem? Please describe.
I'm always frustrated when slicer requires a lot of parameters to work.
Describe the solution you'd like
For the reader-based interface we can check if the reader passed implements
Seeker
as well and if so --- getting the payload size from it is a piece of cake.Additional context
#539, this can't replace it, but can be a nice amendment, buffers and files implement
Seek()
.The text was updated successfully, but these errors were encountered: