Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 10 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(3)
我们在 2.8 中“偿还”了大部分积累的技术债务。我们没有保留现在或将来计划更改的设计错误列表。事实上,我认为未来几年我们将看到一个相当稳定的阶段,其中大部分精力将花在获得出色的 API 和库以及解决并行性挑战上。
We "paid" most accumulated technical debt in 2.8. We maintain no list of design mistakes that are scheduled for changing now or in the future. In fact I think we'll see a pretty stable phase for the next years where most energy will be spent on getting great APIs and libraries and figuring out the parallelism challenge.
这类信息可以在 Scala 论坛“内部” 中更容易获得 或 Scala Debate,尽管这些论坛位于 移至 google 群组论坛的流程:
即将推出:Google 群组 scala-internals。
目前,关于 Scala 2.9 的唯一信息是此路线图(2010 年 8 月):
That kind of information would be more readily available at the Scala forum "internal" or Scala Debate, although those forums are in the process to being moved to google-groups forums:
Soon: Google groups scala-internals.
Right now, the only information on Scala 2.9 is this roadmap (august 2010):
当然,总是有这样的: http://www.scala-lang.org/node/8579< /a>
Of course, there's always this: http://www.scala-lang.org/node/8579