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
Do these methods really belong in RxKotlin? #58
Comments
This is why they are here. Almost everything here is just to make code look better. |
I see, thanks. |
You can already use
You can use
This just seem superfluous. Almost no one should be using |
I agree with @JakeWharton here. Pretty much any function that is not an extension function should be removed. These resemble more syntactic saccharine than syntactic sugar. They offer minimal readability benefit and makes moving from RxJava to RxKotlin more convoluted, and many will keep using the RxJava factories anyway. Besides, if people want them that badly they can implement these functions themselves on their domain with little effort, to the point it is not even worth creating a library for. That's the great thing about Kotlin. You can create your own DSL for your needs. @stepango would you like me to put in a PR removing all these functions? |
@thomasnield I'll prefer to deprecate it first and remove it in one of the future releases |
Sounds good. |
Agreed with @JakeWharton, @maxandron and @thomasnield. This functions will be removed in upcoming 1.x and 2.x along with some others. Feel free to reopen this issue for further discussion. |
Hi,
Just wondering about the reasoning behind adding functions such as
deferredObservable
,observable
oremptyObservable
.They do not add anything kotlin specific.
They might help with readability, but do they really belong in RxKotlin?
Or am I missing something?
Thanks
The text was updated successfully, but these errors were encountered: