Skip to content
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

Derive sliced payload size from ReaderSeeker #545

Open
roman-khimov opened this issue Jan 17, 2024 · 0 comments
Open

Derive sliced payload size from ReaderSeeker #545

roman-khimov opened this issue Jan 17, 2024 · 0 comments
Labels
enhancement Improving existing functionality I3 Minimal impact performance More of something per second S4 Routine U4 Nothing urgent

Comments

@roman-khimov
Copy link
Member

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().

@roman-khimov roman-khimov added enhancement Improving existing functionality U4 Nothing urgent S4 Routine I3 Minimal impact performance More of something per second labels Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improving existing functionality I3 Minimal impact performance More of something per second S4 Routine U4 Nothing urgent
Projects
None yet
Development

No branches or pull requests

1 participant