Remove dependency on crossbeam-utils

Author: Kobzol

Cargo.lock

@@ -27,7 +27,6 @@ intern = { path = "../intern" }
 futures = "0.3.5"
 num_cpus = "1.13"
 jobserver = "0.1.21"
-crossbeam-utils = "0.8"
 snap = "1"
 filetime = "0.2.14"
 walkdir = "2"

collector/Cargo.toml

@@ -248,23 +248,22 @@ impl Benchmark {
         // to do this in Cargo today. We would also ideally build in the same
         // target directory, but that's also not possible, as Cargo takes a
         // target-directory global lock during compilation.
-        crossbeam_utils::thread::scope::<_, anyhow::Result<()>>(|s| {
+        std::thread::scope::<_, anyhow::Result<()>>(|s| {
             let server = jobserver::Client::new(num_cpus::get()).context("jobserver::new")?;
             for (profile, prep_dir) in &profile_dirs {
                 let server = server.clone();
-                s.spawn::<_, anyhow::Result<()>>(move |_| {
+                s.spawn::<_, anyhow::Result<()>>(move || {
                     // Panic the thread if an error occurs to make sure that the whole scope will
                     // also panic if there was some error.
                     self.mk_cargo_process(compiler, prep_dir.path(), *profile)
                         .jobserver(server)
                         .run_rustc(false)
-                        .unwrap();
+                        .expect("Preparation failed");
                     Ok(())
                 });
             }
             Ok(())
-        })
-        .expect("Preparation has failed")?;
+        })?;
 
         for (profile, prep_dir) in profile_dirs {
             eprintln!("Running {}: {:?} + {:?}", self.name, profile, scenarios);