raboof commented on issue #1670: URL: https://github.com/apache/pekko/issues/1670#issuecomment-2572863052
This is indeed an unfortunate puzzle. We have public API's that accept `org.apache.pekko.japi.Function` as a parameter. I don't think we should mark `org.apache.pekko.japi.Function` as deprecated when we still have non-deprecated APIs that require it. Replacing those with variants that take `org.apache.pekko.japi.function.Function` is not easy, since having both variants is ambiguous when called with a Java lambda. I don't see an elegant way to make this migration. Perhaps we should just make this breaking change 'in one go' in 2.0.0 without a deprecation cycle - after all, these classes aren't really meant to be used 'on their own', but only in the context of being used as parameters. -- 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: notifications-unsubscr...@pekko.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
