Introduced 'rxjava-scalaz' project.  This project provides some type class instances for Observable.

* Monoid: Observable obviously forms a monoid in terms of concatenation.
* Functor, Applicative, Monad, MonadPlus: Observable can be a Stream-like Monad and can be MonadPlus as well as Monoid.
* Traverse, Foldable: Observable can be Stream-like traversable. __NOTE: The operations for the instance is blocking calls.__
* etc.

About Testing, property based tests are applied by Scalaz's ScalaCheck binding.

For QuickStart, please refer to rx.java.scala.scalaz.examples.RxScalazDemo.
replaced getOne method which is based on promise with toBlocking.first
Ensuring Runnables posted with delay to a Handler are removed when unsubscribed.

This patch ensures the delayed runnables posted to a Handler are properly
removed when Subscription.unsubscribe() is called on the Observable.

The original code returns the subscription from schedule() but is not used
by the callers who instead add the Worker itself as a subsciption.

Signed-off-by: David Marques <dpsmarques@gmail.com>
Using a ScheduledAction in order to ensure correct subscription behaviour.

Signed-off-by: David Marques <dpsmarques@gmail.com>
Join patterns extension for 4..9 and N arity joins.
CRLF fix
Adding ScheduledSubscription to parent in order to properly chain unsubscribe.

Signed-off-by: David Marques <dpsmarques@gmail.com>
IOSSchedulers for RoboVM
Using the correct code style for variable name and removing unused imports.

Signed-off-by: David Marques <dpsmarques@gmail.com>
Bump build tools to 19.1 and android plugin to 0.11

This is to make the project compatible with Studio 0.6.x
RxScala: Add *Option and *OrElse to BlockingObservable
RxScala: Add latest to BlockingObservable
RxScala: Add toFuture to BlockingObservable
RxScala: Add examples for BlockingObservable
Future wil receive NoSuchElementException when the BlockingObservable is empty
Update '***OrElse' to use Option.getOrElse
RxScala: Simplify doOnCompleted/Terminate, finallyDo callback usage
Allow use of the returned subscription to cancel periodic scheduling

The documentation for schedulePeriodically indicates that the returned
subscription can be used to unsubscribe from the periodic action, or to
unschedule it if it has not been scheduled yet. That was the case only
before the first action took place, and it was then impossible to
unsubscribe using the given subscription, although unsubscribing the
worker did work.
Baseline Performance Tests

Start of suite of general performance tests for comparing overall changes.
Merge pull request #1350 from benjchristensen/perf-tests

Baseline Performance Tests