You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm still in the middle of fleshing this out, but roughly:
Removal of all Object methods from rx-core
Scala RxJava usage doesn't depend on runtime class lookup - instead it uses some implicits from Scala function types to Rx Func1, Func2, ..., FuncN to assert type safety while using native Scala closures
Unit tests to demonstrate full coverage of Observable methods using Scala
Given the first point above, this will have to be combined with #204, so that support for dynamic languages continues.
Small addition.
For-comprehension for observable should be supported as well.
It means that Observable should have flatMap, map and withFilter methods.
Good idea. At first glance, I think this could be accomplished by the introduction of an implicit class (ScalaObservable?) wrapping Observable that implements flatMap, map, and withFilter by delegating to mapMany, map, and filter, respectively. As long as all the methods still return an Observable, then we should be OK.
Activity
mairbek commentedon Mar 25, 2013
Small addition.
For-comprehension for observable should be supported as well.
It means that
Observableshould haveflatMap,mapandwithFiltermethods.mattrjacobs commentedon Mar 25, 2013
Good idea. At first glance, I think this could be accomplished by the introduction of an implicit class (
ScalaObservable?) wrappingObservablethat implementsflatMap,map, andwithFilterby delegating tomapMany,map, andfilter, respectively. As long as all the methods still return anObservable, then we should be OK.Merge pull request ReactiveX#208 from cpilsworth/enhancement/207-retr…