scala – 为什么结构化类型的编译时生成技术会阻止单独编译？

Generative techniques create Java interfaces to stand in
for structural types on the JVM. The complexity of such
techniques lies in that all classes that are to be used as
structural types anywhere in the program must implement
the right interfaces. When this is done at compile time,it
prevents separate compilation.

(重点补充)

考虑论文中的autoclose示例：

type Closeable = Any { def close(): Unit }

def autoclose(t: Closeable)(run: Closeable => Unit): Unit = {
   try { run(t) }
   finally { t.close }
}

我们无法为Closeable类型生成一个接口,如下所示：

public interface AnonymousInterface1 {
   public void close();
}

并将我们对autoclose的定义转换为

// UPDATE: using a view bound here,so implicit conversion is applied on-demand
def autoclose[T <% AnonymousInterface1](t: T)(run: T => Unit): Unit = {
   try { run(t) }
   finally { t.close }
}

然后考虑autoclose的呼叫站点：

val fis = new FileInputStream(new File("f.txt"))
autoclose(fis) { ... }

由于fis是FileInputStream,它没有实现AnonymousInterface1,我们需要生成一个包装器：

class FileInputStreamAnonymousInterface1Proxy(val self: FileInputStream) 
      extends AnonymousInterface1 {
   def close() = self.close();
}

object FileInputStreamAnonymousInterface1Proxy {
   implicit def fis2proxy(fis: FileInputStream): FileInputStreamAnonymousInterface1Proxy =
      new FileInputStreamAnonymousInterface1Proxy(fis)
}

我必须遗漏一些东西,但我不清楚它是什么.为什么这种方法会阻止单独编译？