-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Ambiguous method error when using RxConvert from Java #2182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Unfortunately, it's not that simple, because it will break every binary client that already compiled against an older version of |
…of 'from' function to prevent naming clash for Java users. * Do not provide @jvmoverloads for convenience of Java interop * Deprecate ReceiveChannel.asObservable by the way Fixes #2182
Kotlin#2285) * Provide asFlowable and asObservable by their names in binary instead of 'from' function to prevent naming clash for Java users. * Do not provide @jvmoverloads for convenience of Java interop * Deprecate ReceiveChannel.asObservable by the way Fixes Kotlin#2182
Kotlin#2285) * Provide asFlowable and asObservable by their names in binary instead of 'from' function to prevent naming clash for Java users. * Do not provide @jvmoverloads for convenience of Java interop * Deprecate ReceiveChannel.asObservable by the way Fixes Kotlin#2182
While using the extension functions from RxConvert to convert
Flow
toObservable
orFlowable
in Java, we fail to build from an ambiguous method error.asFlowable()
andasObservable()
both have aJVMName
offrom
. The following test case in Java is a way to reproduce this issue:A simple fix could be removing the
JVMName
entirely. Another option is changing theJVMName
to be more specific to the function, but an appropriate name doesn't come to mind.After a solution is decided I would be more than happy to create a PR for a fix.
The text was updated successfully, but these errors were encountered: