Add Scala.js and Scala Native artifacts that have serial behavior?

[SethTisue]

as suggested by @JD557

Pros:

• Convenient for folks who are crossbuilding
• If we add this library to the Toolkit, as I've suggested at https://github.com/scala/toolkit/issues/31 , there is a usual expectation that included libraries are cross-platform. Though we've already included os-lib regardless, which is major precedent

Cons:

• Non-JVM users might be surprised to have their .par using code compile but not get any actual parallelism
  • If we're concerned about this, I suppose we could print a runtime warning to stderr, then provide an API call to suppress the warning

[JD557]

I haven't tested this, but I think a simple solution might be to just change https://github.com/scala/scala-parallel-collections/blob/ec2c34b6d9fb4cc6135cff502250738ed7f49e55/core/src/main/scala/scala/collection/parallel/package.scala#L39 to use parasitic on native and js.

At least I think with that EC Await.result will work on both native and js.

[SethTisue]

At least I think with that EC Await.result will work on both native and js

@sjrd agree?

[sjrd]

Await.result will never link on Scala.js. It doesn't matter what execution context you use. Await.result has the potential to synchronously wait, so it won't link, period.

[WojciechMazur]

With the Scala Native 0.5.0 it would be beneficial to support Scala Native artifacts. With the added multithreading support there should be no issues with using parallel collections and scala.collection.concurrent It is already tested based on Scala 2.12 Junit partests for almost a year now: https://github.com/scala-native/scala-native/pull/3149

[SethTisue]

Wow, cool! Yes, a PR on that would be welcome.