Don't use Scala Futures in Java APIs#1419
Closed
raboof wants to merge 1 commit intoapache:mainfrom
Closed
Conversation
raboof
force-pushed
the
no-scala-futures-in-java
branch
from
a964d1f to
9f74250
Compare
Sketching out apache#1417 - incomplete and notably not bothering with binary compatibility yet, just to illustrate the idea.
raboof
force-pushed
the
no-scala-futures-in-java
branch
from
9f74250 to
90c8498
Compare
Contributor
|
Not sure if this is related but there are methods like |
Member
|
@raboof Would you like to continue this? |
Member
|
#2092 took most of what was in this PR. |
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
4 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.
Sketching out #1417 - incomplete and notably not bothering with binary compatibility yet, just to illustrate the idea.