Open
Conversation
added 2 commits
February 24, 2026 13:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I suggest adding the ability to pass a custom buffer from user code. This would make it possible, in flows where we sequentially iterate over a large table and process records in chunks, to avoid reallocating the buffer. In my case, I need to traverse 5 million rows in batches of 100k when retrieving them from the database. I want to do this using a single array instead of allocating a new one each time.
Why is this not equivalent to a buffering flag?
Because the method returns IEnumerable rather than IAsyncEnumerable. As a result, the non-buffered mode relies on synchronous overloads. We should either change the design accordingly or provide an IAsyncEnumerable counterpart for the method without the buffering flag.