mdedetrich commented on PR #2554: URL: https://github.com/apache/pekko/pull/2554#issuecomment-3621117507
> That is my point. The code is not yet deprecated and I think there is a good chance that Java users have been using it. I don't see why we can't leave the method alone and maybe just add a javadoc mention of more Java friendly methods that we also support. > > It causes us zero overhead to maintain the existing method. While I agree that the PR to deprecate the method should land first in Pekko 1.x series, leaving around the method in 2.0.x series is likely going to be pointless/useless because the only reason it exists is due to deficiencies in the current 1.x Pekko API where it leaks the usage of Scala futures to `javaapi`, a lot of which is actually fixed in 2.0.x series. Actual Java users don't like and don't want to use Scala's future, and I would be shocked if anyone is actually using these methods aside from the usecase I described ergo some `javadsl` returning/accepting a Scala future when it should instead be using `CompletionStage`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
