Removed cached thread pool creation#8
Merged
Conversation
Seems redundant and nobody uses the value of `Executors.newCachedThreadPool`, unless I'm missing something.
Removed cached thread pool creation
Member
|
Well spotted! It must be an artefact left during a debugging session. I feel ashamed to have let this slipped! |
Member
|
Looks like GitHub does not want me to merge this from my phone. I will do that tomorrow. |
Member
|
Released in Wisp 2.2.0 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Seems redundant and nobody uses the value of
Executors.newCachedThreadPool, unless I'm missing something.