Remove deprecated/unused ThreadPoolTypes
#117041
Closed
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.
Only caveat:
ThreadPoolType.fromTypeis used in transport protocol serialization.I was thinking to not introduce a new TV, but to backport this change and add an explicit fallback for v8.last; v8.last will check if it is one of the deprecated / removed in v9 strings, and fallback (defaulting to fixed):
So there will be no chance v9 will ever see these ThreadPoolType strings.