-
Notifications
You must be signed in to change notification settings - Fork 111
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
Using RxJava @Beta/@Experimental features in RxScala #100
Comments
Why don't we add them as extension methods (perhaps using the same markers) so you can import them separately. |
I think we can document two tables for the API compatibility, one for stable APIs, the other for |
@headinthebox for the experimental methods of RxJava Observable, I added them as extension methods in RxScala #146. But for the experimental classes, such as |
Closed. Resolved in 0.25.0 |
What is the current thinking about using features/methods marked as @beta or @experimental in RxJava and exposing them in RxScala?
For example, I was thinking of doing a PR that would make AbstractOnSubscribe available in RxScala with a more Scala idiomatic API. Is that something that would be accepted or should we wait until the feature is marked non-beta/experimental before exposing them in RxScala.
Downside of exposing beta/experimental methods in RxScala is that we tie each RxScala version tighter to a specific RxJava release, with the upside being of making the beta/experimental features available earlier with a Scala interface.
The text was updated successfully, but these errors were encountered: