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.

Sign up for GitHub

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

Jump to bottom

Exposing abortablePromise and abortableAsyncIterable directly. #2031

Closed
bartlomieju opened this issue Mar 15, 2022 · 0 comments · Fixed by #2034
Closed

Exposing abortablePromise and abortableAsyncIterable directly. #2031

bartlomieju opened this issue Mar 15, 2022 · 0 comments · Fixed by #2034

Comments

@bartlomieju
Copy link
Member

Discussed in https://github.com/denoland/deno_std/discussions/2030

Originally posted by harrysolovay March 15, 2022
The abortablePromise and abortableAsyncIterable utilities are exposed only through abortable, which wraps the two. Might it make sense to export them directly? In my situation, I need only abortablePromise, and would prefer to not include the code of abortableAsyncIterable. Thoughts would be greatly appreciated!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(async): expose asyncPromise and asyncAsyncIterable kt3k/deno_std
1 participant
@bartlomieju