diff options
| author | Paul Phillips <paulp@improving.org> | 2012-08-02 10:07:19 -0700 |
|---|---|---|
| committer | Paul Phillips <paulp@improving.org> | 2012-08-11 20:27:46 -0700 |
| commit | a55788e275faed91cb9223686a3aef6ee54213a8 (patch) | |
| tree | 4ac92fc704d7e06edb38680114321309c84dbd5b /test/files/neg/t5148.check | |
| parent | 4459e5abb2b765cbdca34eb19c5d8b705203f771 (diff) | |
| download | scala-a55788e275faed91cb9223686a3aef6ee54213a8.tar.gz scala-a55788e275faed91cb9223686a3aef6ee54213a8.tar.bz2 scala-a55788e275faed91cb9223686a3aef6ee54213a8.zip | |
More resilience to missing classes.
The situation (I don't know how to make partest test this) is
package s
class A ; class S { def f(): A = ??? }
If one compiles this and removes A.class, should references to
class S cause the compiler to explode eagerly and fail to load S,
or explode lazily if and when it needs to know something about A?
This patch takes us from the former strategy to the latter.
Review by @xeno-by.
Diffstat (limited to 'test/files/neg/t5148.check')
| -rw-r--r-- | test/files/neg/t5148.check | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/test/files/neg/t5148.check b/test/files/neg/t5148.check index 96eb1fd364..6edfdf2b1e 100644 --- a/test/files/neg/t5148.check +++ b/test/files/neg/t5148.check @@ -1,2 +1,3 @@ -error: bad reference while unpickling Imports.class: term memberHandlers not found in scala.tools.nsc.interpreter.IMain -one error found +error: bad symbolic reference to value global in class IMain - referenced from t5148.scala (a classfile may be missing) +error: bad symbolic reference to value memberHandlers in class IMain - referenced from t5148.scala (a classfile may be missing) +two errors found |