redesign json-stream functions to rely on AsyncGenerator #48
Conversation
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
ndeloof
force-pushed
the
AsyncGenerator
branch
4 times, most recently
from
9960886 to
f2ca3c3
Compare
Signed-off-by: Nicolas De Loof <[email protected]>
ndeloof
force-pushed
the
AsyncGenerator
branch
from
f2ca3c3 to
45f7b7b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
- What I did
replace use of a callback with an AsyncGenerator in json-stream APIs
- How I did it
claude.ai
- How to verify it
- Human readable description for the release notes
- A picture of a cute animal (not mandatory but encouraged)