Derive sliced payload size from ReaderSeeker #212

Open
opened 2025-12-28 18:07:27 +00:00 by sami · 0 comments
Owner

Originally created by @roman-khimov on GitHub (Jan 17, 2024).

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

Originally created by @roman-khimov on GitHub (Jan 17, 2024). ## 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()`.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-sdk-go#212
No description provided.