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 much as I'd like to avoid it, it seems like some kind of hint system would be useful for telling who should allocate buffers and of what size.
Ideally, this would be done out of the regular pull flow (to avoid passing like 7 arguments every time). So, probably going to be connected to an other (yet to be made) issue about doing some kind of "construct" flow...
One piece of contention in the current design of the sink API is whom allocates the buffer. If I have data already in buffers that needs to be written to a socket or disk it doesn't make sense for the sink to allocate a write buffer and tell me to copy values into it.
The text was updated successfully, but these errors were encountered:
As much as I'd like to avoid it, it seems like some kind of hint system would be useful for telling who should allocate buffers and of what size.
Ideally, this would be done out of the regular pull flow (to avoid passing like 7 arguments every time). So, probably going to be connected to an other (yet to be made) issue about doing some kind of "construct" flow...
See #30 (comment)
The text was updated successfully, but these errors were encountered: