This repository was archived by the owner on Dec 3, 2019. It is now read-only.
Add AsyncObjectPool.use to combine take and giveBack #53
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.
This seems like a common use case, and as long as the provided function doesn't hold onto the provided item it should be safe. Is this reasonable? Is it sufficiently non-trivial for addition? It eliminates duplicate code in ConnectionPool.
I'm working up to writing a withTransaction-like function but want to make sure I'm on the right track.