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

Should Pool#dispose call destroy() in a blocking fashion #6

Closed
simonbasle opened this issue Feb 15, 2019 · 1 comment
Closed

Should Pool#dispose call destroy() in a blocking fashion #6

simonbasle opened this issue Feb 15, 2019 · 1 comment
Milestone
0.0.1.M1

Comments

@simonbasle
Copy link
Member

If so, should we also provide an async disposal method that doesn't block?
@simonbasle simonbasle added the status/need-design This needs more in depth design work label Feb 15, 2019
@simonbasle simonbasle mentioned this issue Feb 15, 2019
Closed
@simonbasle simonbasle removed the status/need-design This needs more in depth design work label Apr 25, 2019
@simonbasle
Copy link
Member Author

Switched to an async call of destroyHandler in f58a528

@simonbasle simonbasle added this to the 0.0.1.M1 milestone May 9, 2019
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
0.0.1.M1
Development

No branches or pull requests
1 participant
@simonbasle