Scala 2.8 突破
在 Scala 2.8 中,scala.collection.package.scala
中有一个对象:
def breakOut[From, T, To](implicit b : CanBuildFrom[Nothing, T, To]) =
new CanBuildFrom[From, T, To] {
def apply(from: From) = b.apply() ; def apply() = b.apply()
}
我被告知这会导致:
> import scala.collection.breakOut
> val map : Map[Int,String] = List("London", "Paris").map(x => (x.length, x))(breakOut)
map: Map[Int,String] = Map(6 -> London, 5 -> Paris)
这里发生了什么?为什么 breakOut
被作为参数调用到我的 List
?
In Scala 2.8, there is an object in scala.collection.package.scala
:
def breakOut[From, T, To](implicit b : CanBuildFrom[Nothing, T, To]) =
new CanBuildFrom[From, T, To] {
def apply(from: From) = b.apply() ; def apply() = b.apply()
}
I have been told that this results in:
> import scala.collection.breakOut
> val map : Map[Int,String] = List("London", "Paris").map(x => (x.length, x))(breakOut)
map: Map[Int,String] = Map(6 -> London, 5 -> Paris)
What is going on here? Why is breakOut
being called as an argument to my List
?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
答案可以在
map
的定义中找到:注意它有两个参数。第一个是你的函数,第二个是隐式函数。如果您不提供该隐含信息,Scala 将选择最具体可用的一个。
关于
breakOut
那么,
breakOut
的用途是什么?考虑针对该问题给出的示例,您获取一个字符串列表,将每个字符串转换为一个元组(Int, String)
,然后从中生成一个Map
。最明显的方法是生成一个中间List[(Int, String)]
集合,然后对其进行转换。鉴于
map
使用Builder
来生成结果集合,是不是可以跳过中间的List
并将结果直接收集到地图?显然,是的,确实如此。然而,要做到这一点,我们需要将正确的CanBuildFrom
传递给map
,而这正是breakOut
所做的。然后,让我们看一下
breakOut
的定义:请注意,
breakOut
是参数化的,并且它返回CanBuildFrom
的实例。碰巧,类型From
、T
和To
已经被推断出来,因为我们知道map
是期待CanBuildFrom[List[String], (Int, String), Map[Int, String]]
。因此:作为结论,让我们检查一下
breakOut
本身接收到的隐式内容。它的类型为CanBuildFrom[Nothing,T,To]
。我们已经知道所有这些类型,因此可以确定我们需要一个隐式类型CanBuildFrom[Nothing,(Int,String),Map[Int,String]]
。但有这样的定义吗?让我们看一下
CanBuildFrom
的定义:因此
CanBuildFrom
在其第一个类型参数上是逆变的。因为Nothing
是一个底层类(即,它是所有东西的子类),这意味着任何类都可以用来代替Nothing
。由于存在这样的构建器,Scala 可以使用它来生成所需的输出。
关于构建器
Scala 集合库中的许多方法包括获取原始集合、以某种方式处理它(在
map
的情况下,转换每个元素)以及存储结果在一个新的集合中。为了最大化代码重用,结果的存储是通过构建器(scala.collection.mutable.Builder)完成的,它基本上支持两种操作:追加元素和返回由此产生的集合。此结果集合的类型将取决于构建器的类型。因此,
List
构建器将返回List
,Map
构建器将返回Map
,依此类推。map
方法的实现不需要关心结果的类型:构建器会处理它。另一方面,这意味着
map
需要以某种方式接收此构建器。设计 Scala 2.8 Collections 时面临的问题是如何选择最好的构建器。例如,如果我要编写Map('a' -> 1).map(_.swap)
,我想得到一个Map(1 -> ' a')
返回。另一方面,Map('a' -> 1).map(_._1)
不能返回Map
(它返回一个可迭代
)。从表达式的已知类型生成最佳的
Builder
的魔力是通过此CanBuildFrom
隐式执行的。关于
CanBuildFrom
为了更好地解释发生的情况,我将给出一个示例,其中映射的集合是
Map
而不是列表
。稍后我会返回List
。现在,考虑这两个表达式:第一个返回一个
Map
,第二个返回一个Iterable
。返回合适集合的神奇之处在于CanBuildFrom
的工作。让我们再次考虑一下map
的定义来理解它。map
方法继承自TraversableLike
。它在B
和That
上进行参数化,并使用类型参数A
和Repr
,这些参数对班级。让我们一起看看这两个定义:TraversableLike
类定义为:要了解
A
和Repr
从何而来,让我们考虑的定义>Map
本身:因为
TraversableLike
被扩展Map
、A
和Repr
的所有特征继承可以从他们中的任何一个继承。不过,最后一个获得了优先权。因此,根据不可变Map
的定义以及将其连接到TraversableLike
的所有特征,我们有:如果您传递
Map[Int, String]
沿着链一路向下,我们发现传递给TraversableLike
并因此被map
使用的类型是:例如,第一个映射正在接收
((Int, String)) => 类型的函数(Int, Int)
并且第二个映射正在接收((Int, String)) => 类型的函数字符串
。我使用双括号来强调它是接收到的元组,因为这是我们看到的A
类型。有了这些信息,我们就可以考虑其他类型。
我们可以看到第一个
map
返回的类型是Map[Int,Int]
,第二个是Iterable[String]
。查看map
的定义,很容易看出这些是That
的值。但它们从哪里来?如果我们查看所涉及的类的伴生对象内部,我们会看到一些提供它们的隐式声明。在对象
Map
上:以及在对象
Iterable
上,其类由Map
扩展:这些定义为参数化
CanBuildFrom
提供工厂>。Scala 将选择最具体的隐式可用。在第一种情况下,它是第一个
CanBuildFrom
。在第二种情况下,由于第一个不匹配,因此它选择了第二个CanBuildFrom
。回到问题
让我们看一下问题的代码、
List
和map
的定义(再次)以了解类型如何推断:List("London", "Paris")
的类型是List[String]
,因此类型A
和
为:TraversableLike
上定义的 Repr(x => (x.length, x))
的类型为(String) => (Int, String)
,所以B
的类型是:最后一个未知类型,
That
就是map
结果的类型code>,我们也已经有了:所以,
这意味着
breakOut
必须返回CanBuildFrom[List[String], (Int, String), Map 的类型或子类型[整数,字符串]]
。The answer is found on the definition of
map
:Note that it has two parameters. The first is your function and the second is an implicit. If you do not provide that implicit, Scala will choose the most specific one available.
About
breakOut
So, what's the purpose of
breakOut
? Consider the example given for the question, You take a list of strings, transform each string into a tuple(Int, String)
, and then produce aMap
out of it. The most obvious way to do that would produce an intermediaryList[(Int, String)]
collection, and then convert it.Given that
map
uses aBuilder
to produce the resulting collection, wouldn't it be possible to skip the intermediaryList
and collect the results directly into aMap
? Evidently, yes, it is. To do so, however, we need to pass a properCanBuildFrom
tomap
, and that is exactly whatbreakOut
does.Let's look, then, at the definition of
breakOut
:Note that
breakOut
is parameterized, and that it returns an instance ofCanBuildFrom
. As it happens, the typesFrom
,T
andTo
have already been inferred, because we know thatmap
is expectingCanBuildFrom[List[String], (Int, String), Map[Int, String]]
. Therefore:To conclude let's examine the implicit received by
breakOut
itself. It is of typeCanBuildFrom[Nothing,T,To]
. We already know all these types, so we can determine that we need an implicit of typeCanBuildFrom[Nothing,(Int,String),Map[Int,String]]
. But is there such a definition?Let's look at
CanBuildFrom
's definition:So
CanBuildFrom
is contra-variant on its first type parameter. BecauseNothing
is a bottom class (ie, it is a subclass of everything), that means any class can be used in place ofNothing
.Since such a builder exists, Scala can use it to produce the desired output.
About Builders
A lot of methods from Scala's collections library consists of taking the original collection, processing it somehow (in the case of
map
, transforming each element), and storing the results in a new collection.To maximize code reuse, this storing of results is done through a builder (
scala.collection.mutable.Builder
), which basically supports two operations: appending elements, and returning the resulting collection. The type of this resulting collection will depend on the type of the builder. Thus, aList
builder will return aList
, aMap
builder will return aMap
, and so on. The implementation of themap
method need not concern itself with the type of the result: the builder takes care of it.On the other hand, that means that
map
needs to receive this builder somehow. The problem faced when designing Scala 2.8 Collections was how to choose the best builder possible. For example, if I were to writeMap('a' -> 1).map(_.swap)
, I'd like to get aMap(1 -> 'a')
back. On the other hand, aMap('a' -> 1).map(_._1)
can't return aMap
(it returns anIterable
).The magic of producing the best possible
Builder
from the known types of the expression is performed through thisCanBuildFrom
implicit.About
CanBuildFrom
To better explain what's going on, I'll give an example where the collection being mapped is a
Map
instead of aList
. I'll go back toList
later. For now, consider these two expressions:The first returns a
Map
and the second returns anIterable
. The magic of returning a fitting collection is the work ofCanBuildFrom
. Let's consider the definition ofmap
again to understand it.The method
map
is inherited fromTraversableLike
. It is parameterized onB
andThat
, and makes use of the type parametersA
andRepr
, which parameterize the class. Let's see both definitions together:The class
TraversableLike
is defined as:To understand where
A
andRepr
come from, let's consider the definition ofMap
itself:Because
TraversableLike
is inherited by all traits which extendMap
,A
andRepr
could be inherited from any of them. The last one gets the preference, though. So, following the definition of the immutableMap
and all the traits that connect it toTraversableLike
, we have:If you pass the type parameters of
Map[Int, String]
all the way down the chain, we find that the types passed toTraversableLike
, and, thus, used bymap
, are:Going back to the example, the first map is receiving a function of type
((Int, String)) => (Int, Int)
and the second map is receiving a function of type((Int, String)) => String
. I use the double parenthesis to emphasize it is a tuple being received, as that's the type ofA
as we saw.With that information, let's consider the other types.
We can see that the type returned by the first
map
isMap[Int,Int]
, and the second isIterable[String]
. Looking atmap
's definition, it is easy to see that these are the values ofThat
. But where do they come from?If we look inside the companion objects of the classes involved, we see some implicit declarations providing them. On object
Map
:And on object
Iterable
, whose class is extended byMap
:These definitions provide factories for parameterized
CanBuildFrom
.Scala will choose the most specific implicit available. In the first case, it was the first
CanBuildFrom
. In the second case, as the first did not match, it chose the secondCanBuildFrom
.Back to the Question
Let's see the code for the question,
List
's andmap
's definition (again) to see how the types are inferred:The type of
List("London", "Paris")
isList[String]
, so the typesA
andRepr
defined onTraversableLike
are:The type for
(x => (x.length, x))
is(String) => (Int, String)
, so the type ofB
is:The last unknown type,
That
is the type of the result ofmap
, and we already have that as well:So,
That means
breakOut
must, necessarily, return a type or subtype ofCanBuildFrom[List[String], (Int, String), Map[Int, String]]
.我想以丹尼尔的回答为基础。它非常彻底,但正如评论中所述,它没有解释突破的作用。
摘自回复:对显式构建器的支持 (2009-10-23),这就是我认为突破的作用:
它向编译器提供隐式选择哪个 Builder 的建议(本质上它允许编译器选择它认为最适合情况的工厂.)
例如,请参见以下内容:
您可以看到编译器隐式选择返回类型以最好地匹配预期类型。根据您声明接收变量的方式,您会得到不同的结果。
以下是指定构建器的等效方法。请注意,在这种情况下,编译器将根据构建器的类型推断预期类型:
I'd like to build upon Daniel's answer. It was very thorough, but as noted in the comments, it doesn't explain what breakout does.
Taken from Re: Support for explicit Builders (2009-10-23), here is what I believe breakout does:
It gives the compiler a suggestion as to which Builder to choose implicitly (essentially it allows the compiler to choose which factory it thinks fits the situation best.)
For example, see the following:
You can see the return type is implicitly chosen by the compiler to best match the expected type. Depending on how you declare the receiving variable, you get different results.
The following would be an equivalent way to specify a builder. Note in this case, the compiler will infer the expected type based on the builder's type:
Daniel Sobral 的回答很棒,应该与 Architecture 一起阅读Scala 集合(《Scala 编程》第 25 章)。
我只是想详细说明一下为什么叫
breakOut
:为什么叫
breakOut
?因为我们想要突破一种类型并进入另一种类型:
从什么类型突破到什么类型?让我们以
Seq
上的map
函数为例:如果我们想直接通过映射序列的元素来构建一个 Map,例如:
编译器会抱怨:
原因是 Seq 只知道如何构建另一个 Seq(即有一个隐式的 CanBuildFrom[Seq[_], B, Seq[B]] 构建器工厂可用,但没有 构建器工厂(从 Seq 到 Map)。
为了编译,我们需要以某种方式
breakOut
类型要求,并能够构造一个生成器,为<要使用的 code>map 函数。正如 Daniel 所解释的,breakOut 具有以下签名:
Nothing 是所有类的子类,因此任何构建器工厂都可以替换隐式 b:CanBuildFrom[Nothing, T, To] 。如果我们使用breakOut函数提供隐式参数:
它会编译,因为
breakOut
能够提供所需的CanBuildFrom[Seq[(String, Int)], (String, Int), Map[String, Int]]
,而编译器能够找到CanBuildFrom[Map[_, _], (A, B), Map[A, B]]
,代替CanBuildFrom[Nothing, T, To]
,用于 BreakOut 创建实际的构建器。请注意,
CanBuildFrom[Map[_, _], (A, B), Map[A, B]]
是在 Map 中定义的,并且只需启动一个MapBuilder
即可使用底层地图。希望这能解决问题。
Daniel Sobral's answer is great, and should be read together with Architecture of Scala Collections (Chapter 25 of Programming in Scala).
I just wanted to elaborate on why it is called
breakOut
:Why is it called
breakOut
?Because we want to break out of one type and into another:
Break out of what type into what type? Lets look at the
map
function onSeq
as an example:If we wanted to build a Map directly from mapping over the elements of a sequence such as:
The compiler would complain:
The reason being that Seq only knows how to build another Seq (i.e. there is an implicit
CanBuildFrom[Seq[_], B, Seq[B]]
builder factory available, but there is NO builder factory from Seq to Map).In order to compile, we need to somehow
breakOut
of the type requirement, and be able to construct a builder that produces a Map for themap
function to use.As Daniel has explained, breakOut has the following signature:
Nothing
is a subclass of all classes, so any builder factory can be substituted in place ofimplicit b: CanBuildFrom[Nothing, T, To]
. If we used the breakOut function to provide the implicit parameter:It would compile, because
breakOut
is able to provide the required type ofCanBuildFrom[Seq[(String, Int)], (String, Int), Map[String, Int]]
, while the compiler is able to find an implicit builder factory of typeCanBuildFrom[Map[_, _], (A, B), Map[A, B]]
, in place ofCanBuildFrom[Nothing, T, To]
, for breakOut to use to create the actual builder.Note that
CanBuildFrom[Map[_, _], (A, B), Map[A, B]]
is defined in Map, and simply initiates aMapBuilder
which uses an underlying Map.Hope this clears things up.
通过一个简单的例子来了解
breakOut
的作用:A simple example to understand what
breakOut
does: