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

perf: directly pass an async iterable to the fetch body #690

Closed
Tracked by #675
KnorpelSenf opened this issue Dec 15, 2024 · 2 comments
Closed
Tracked by #675

perf: directly pass an async iterable to the fetch body #690

KnorpelSenf opened this issue Dec 15, 2024 · 2 comments
Labels
wontfix This will not be worked on

Comments

@KnorpelSenf
Copy link
Member

Deno supports sending async iterables. We should investigate which runtimes support this and then save the useless conversion step to web streams.

@KnorpelSenf KnorpelSenf mentioned this issue Dec 15, 2024
48 tasks
@KnorpelSenf KnorpelSenf changed the title feat: directly pass an async iterable to the fetch body perf: directly pass an async iterable to the fetch body Dec 16, 2024
@KnorpelSenf
Copy link
Member Author

This isn't following the fetch spec, though. Should we still go ahead?

@KnorpelSenf
Copy link
Member Author

There isn't really a bug enough advantage for this in order for us to break the spec.

@KnorpelSenf KnorpelSenf added the wontfix This will not be worked on label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant