Pipeline: Remove dependancy on rayon_futures

This requires a RUSTFLAG to be set before hand for rayon to build.
This brakes a lot of tools like rls and clippy by default and
require special configs for itnegration.

Additionally, rayon_futures is still 0.1 and not much work seem
to have gone into it. Ideally it should be replased with the tokio
runtime/threadpool.

podcasts-data/Cargo.toml

@@ -11,7 +11,6 @@ derive_builder = "0.5.1"
 lazy_static = "1.1.0"
 log = "0.4.4"
 rayon = "1.0.2"
-rayon-futures = "0.1.0"
 rfc822_sanitizer = "0.3.3"
 rss = "1.5.0"
 url = "1.7.1"

podcasts-data/src/lib.rs

@@ -80,7 +80,6 @@ extern crate hyper_tls;
 extern crate native_tls;
 extern crate num_cpus;
 extern crate rayon;
-extern crate rayon_futures;
 extern crate rfc822_sanitizer;
 extern crate rss;
 extern crate tokio_core;

podcasts-data/src/pipeline.rs

@@ -11,8 +11,6 @@ use hyper_tls::HttpsConnector;
 use tokio_core::reactor::Core;
 
 use num_cpus;
-use rayon;
-use rayon_futures::ScopeFutureExt;
 
 use errors::DataError;
 use Source;
@@ -55,7 +53,7 @@ where
 {
     sources
         .and_then(clone!(client => move |s| s.into_feed(client.clone())))
-        .and_then(|feed| rayon::scope(|s| s.spawn_future(feed.index())))
+        .and_then(|feed| feed.index())
         // the stream will stop at the first error so
         // we ensure that everything will succeded regardless.
         .map_err(|err| error!("Error: {}", err))