3

鉴于以下情况:

trait Fruit

class Apple extends Fruit
class Orange extends Fruit

case class Crate[T](value:T)

def p(c:Crate[Fruit]) {  }

val cra = Crate(new Apple)
val cro = Crate(new Orange)

由于 Crate 是不变的,我不能执行以下操作(如预期的那样):

scala> val fruit:Crate[Fruit] = cra
<console>:10: error: type mismatch;
 found   : Crate[Apple]
 required: Crate[Fruit]
       val fruit:Crate[Fruit] = cra
                                ^

scala> val fruit:Crate[Fruit] = cro
<console>:10: error: type mismatch;
 found   : Crate[Orange]
 required: Crate[Fruit]
       val fruit:Crate[Fruit] = cro

scala> p(cra)
<console>:12: error: type mismatch;
 found   : Crate[Apple]
 required: Crate[Fruit]
       p(cra)
         ^

scala> p(cro)
<console>:12: error: type mismatch;
 found   : Crate[Orange]
 required: Crate[Fruit]
       p(cro)

但是,当 Crate 不是协变的时,为什么我可以用这些调用方法 p?:

scala> p(Crate(new Apple))
Crate(line2$object$$iw$$iw$Apple@35427e6e)

scala> p(Crate(new Orange))
Crate(line3$object$$iw$$iw$Orange@33dfeb30)

我是否错过了一些基本的方差原则?

4

1 回答 1

6

在后一种情况下,编译器假定您希望它工作并且实际上说

p(Crate( (new Apple): Fruit ))

这是完全可以的。就像你手动做的一样

val f: Fruit = new Apple   // totally fine
p(Crate(f))                // Also totally fine

这只是编译器应用的巨大魔法的一小部分,它试图弄清楚你对类型的含义,而不是让你全部输入。

于 2011-04-11T00:47:49.743 回答