为什么未来会挂在解释器上？

Question

以下一行代码在 Scala REPL 中挂起

import scala.concurrent.ExecutionContext.Implicits.global 
import scala.concurrent.{Future, future, Await}
import scala.concurrent.duration._

def fib(n: Int): Int = {println(n + " is handeled by " + Thread.currentThread.getName) ; if (n < 2) n else Await.result( Future.sequence(List(1,2) map (i => Future{println(n-i); n-i} map fib)) map (_.sum), Duration.Inf)} ; fib(3)

它的核心是

val lf: List[Future[Int]] = List(1,2) map (i => Future{n-i} map fib)
val f: Future[List[Int]] = Future.sequence(lf)
Await.result(f, Inf)

它也挂在 ammonite 解释器中。它更高级，允许中断执行，堆栈跟踪可能会告诉你一些事情

def fib(n: Int): Int = {println(n + " is handeled by " + Thread.currentThread.getName) ; if (n < 2) n else Await.result( Future.sequence(List(1,2) map (i => Future{println(n-i); n-i} map fib)) map (_.sum), Duration.Inf)} ; fib(3) 
3 is handeled by main
1
2
^C
Interrupted!
java.lang.NoClassDefFoundError: Could not initialize class ammonite.session.cmd3$
        at ammonite.session.cmd3$$anonfun$fib$$anonfun$apply.apply$mcII$sp(cmd3.scala:1)
        at ammonite.session.cmd3$$anonfun$fib$$anonfun$apply.apply(cmd3.scala:1)
        at ammonite.session.cmd3$$anonfun$fib$$anonfun$apply.apply(cmd3.scala:1)
        at scala.util.Success$$anonfun$map.apply(Try.scala:237)
        at scala.util.Try$.apply(Try.scala:192)
        at scala.util.Success.map(Try.scala:237)
        at scala.concurrent.Future$$anonfun$map.apply(Future.scala:237)
        at scala.concurrent.Future$$anonfun$map.apply(Future.scala:237)
        at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32)
        at scala.concurrent.impl.ExecutionContextImpl$AdaptedForkJoinTask.exec(ExecutionContextImpl.scala:121)
        at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
        at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.pollAndExecAll(ForkJoinPool.java:1253)
        at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1346)
        at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
        at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
java.lang.NoClassDefFoundError: Could not initialize class ammonite.session.cmd3$
        at ammonite.session.cmd3$$anonfun$fib$$anonfun$apply.apply$mcII$sp(cmd3.scala:1)
        at ammonite.session.cmd3$$anonfun$fib$$anonfun$apply.apply(cmd3.scala:1)
        at ammonite.session.cmd3$$anonfun$fib$$anonfun$apply.apply(cmd3.scala:1)
        at scala.util.Success$$anonfun$map.apply(Try.scala:237)
        at scala.util.Try$.apply(Try.scala:192)
        at scala.util.Success.map(Try.scala:237)
        at scala.concurrent.Future$$anonfun$map.apply(Future.scala:237)
        at scala.concurrent.Future$$anonfun$map.apply(Future.scala:237)
        at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32)
        at scala.concurrent.impl.ExecutionContextImpl$AdaptedForkJoinTask.exec(ExecutionContextImpl.scala:121)
        at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
        at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
        at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
        at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
ubuntu-workspace@

如您所见，代码表示 n=3 is handeled by main，打印 1 和 2 并挂起。这意味着期货已经开始但还没有结束。他们不会按照地图的要求继续撒谎。我可以用 Future{fib(n-i)} 替换 Future{n-i} map fib 但没有任何变化。同时，代码在 Scastie 中正常进行。这表明行为在很大程度上取决于上下文。

Answer 1

这是一个关于在对象初始值设定项中启动线程的重复问题。

快速解决方法是使用 scala -Yrepl-class-based。

相关问题：Scala: Parallel collection in object initializer causes a program to hang

为什么未来会挂在解释器上？

Why does the future hang in the interpreter?

multithreading

scala

future

freeze