This repository has been archived by the owner on Aug 29, 2022. It is now read-only.
Backpedal on hoisting PreferredExecutor into FutureProtocol #272
Conversation
This file contains 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
zwaldowski
added a commit
that referenced
this pull request
Jan 12, 2019
Backpedal on hoisting PreferredExecutor into FutureProtocol
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What's in this pull request?
Reverts a semi-accidental change from #216 that's an upgrade pain and provides no benefit. Deferred already has
Executoras public name, so it makes more sense forPreferredExecutorto live in the sample place.Testing
No changes.
API Changes
Should be non-breaking for most users, and closes the gap when upgrading Deferred 3.0 to 4.0.