forked from scala/scala
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
SI-3452 Correct Java generic signatures for mixins, static forwarders
[Parts of this patch and some of the commentary are from @paulp] This took me so long to figure out I can't even tell you. Partly because there were two different bugs, one which only arose for trait forwarders and one for mirror class forwarders, and every time I'd make one set of tests work another set would start failing. The runtime failures associated with these bugs were fairly well hidden because you usually have to go through java to encounter them: scala doesn't pay that much attention to generic signatures, so they can be wrong and scala might still generate correct code. But java is not so lucky. Bug #1) During mixin composition, classes which extend traits receive forwarders to the implementations. An attempt was made to give these the correct info (in method "cloneBeforeErasure") but it was prone to giving the wrong answer, because: the key attribute which the forwarder must capture is what the underlying method will erase to *where the implementation is*, not how it appears to the class which contains it. That means the signature of the forwarder must be no more precise than the signature of the inherited implementation unless additional measures will be taken. This subtle difference will put on an unsubtle show for you in test run/t3452.scala. trait C[T] trait Search[M] { def search(input: M): C[Int] = null } object StringSearch extends Search[String] { } StringSearch.search("test"); // java // java.lang.NoSuchMethodError: StringSearch.search(Ljava/lang/String;)LC; The principled thing to do here would be to create a pair of methods in the host class: a mixin forwarder with the erased signature `(String)C[Int]`, and a bridge method with the same erased signature as the trait interface facet. But, this turns out to be pretty hard to retrofit onto the current setup of Mixin and Erasure, mostly due to the fact that mixin happens after erasure which has already taken care of bridging. For a future, release, we should try to move all bridging after mixin, and pursue this approach. But for now, what can we do about `LinkageError`s for Java clients? This commit simply checks if the pre-erasure method signature that we generate for the trait forward erases identically to that of the interface method. If so, we can be precise. If not, we emit the erased signature as the generic signature. Bug #2) The same principle is at work, at a different location. During genjvm, objects without declared companion classes are given static forwarders in the corresponding class, e.g. object Foo { def bar = 5 } which creates these classes (taking minor liberties): class Foo$ { static val MODULE$ = new Foo$ ; def bar = 5 } class Foo { static def bar = Foo$.MODULE$.bar } In generating these, genjvm circumvented the usual process whereby one creates a symbol and gives it an info, preferring to target the bytecode directly. However generic signatures are calculated from symbol info (in this case reusing the info from the module class.) Lacking even the attempt which was being made in mixin to "clone before erasure", we would have runtime failures of this kind: abstract class Foo { type T def f(x: T): List[T] = List() } object Bar extends Foo { type T = String } Bar.f(""); // java // java.lang.NoSuchMethodError: Bar.f(Ljava/lang/String;)Lscala/collection/immutable/List; Before/after this commit: < signature f (Ljava/lang/String;)Lscala/collection/immutable/List<Ljava/lang/String;>; --- > signature f (Ljava/lang/Object;)Lscala/collection/immutable/List<Ljava/lang/Object;>; This takes the warning count for compiling collections under `-Ycheck:jvm` from 1521 to 26.
- Loading branch information
Showing
31 changed files
with
717 additions
and
72 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
class Base[Coll] { | ||
trait Transformed[S] { | ||
lazy val underlying: Coll = ??? | ||
} | ||
} | ||
|
||
class Derived extends Base[String] { | ||
class C extends Transformed[Any] | ||
} | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
class Test$bar1$ { | ||
public java.lang.String Test$bar1$.f(java.lang.Object) | ||
public java.lang.Object Test$bar1$.f(java.lang.Object) <bridge> <synthetic> | ||
public java.lang.String Test$bar1$.g(java.lang.String) | ||
public java.lang.Object Test$bar1$.g(java.lang.Object) <bridge> <synthetic> | ||
public java.lang.String Test$bar1$.g(java.lang.Object) <bridge> <synthetic> | ||
public java.lang.Object Test$bar1$.h(java.lang.Object) | ||
} | ||
|
||
class Test$bar2$ { | ||
public java.lang.Object Test$bar2$.f(java.lang.String) | ||
public java.lang.Object Test$bar2$.f(java.lang.Object) <bridge> <synthetic> | ||
public java.lang.String Test$bar2$.g(java.lang.String) | ||
public java.lang.Object Test$bar2$.g(java.lang.Object) <bridge> <synthetic> | ||
public java.lang.Object Test$bar2$.g(java.lang.String) <bridge> <synthetic> | ||
public java.lang.Object Test$bar2$.h(java.lang.Object) | ||
} | ||
|
||
class Test$bar3$ { | ||
public java.lang.String Foo3.f(java.lang.Object) | ||
generic: public java.lang.String Foo3.f(T) | ||
public java.lang.Object Foo3.f(java.lang.Object) <bridge> <synthetic> | ||
public java.lang.String Test$bar3$.g(java.lang.String) | ||
public java.lang.Object Test$bar3$.g(java.lang.Object) <bridge> <synthetic> | ||
public java.lang.String Test$bar3$.g(java.lang.Object) <bridge> <synthetic> | ||
public java.lang.Object Foo3.h(java.lang.Object) | ||
} | ||
|
||
class Test$bar4$ { | ||
public java.lang.Object Foo4.f(java.lang.String) | ||
generic: public R Foo4.f(java.lang.String) | ||
public java.lang.Object Foo4.f(java.lang.Object) <bridge> <synthetic> | ||
public java.lang.String Test$bar4$.g(java.lang.String) | ||
public java.lang.Object Test$bar4$.g(java.lang.Object) <bridge> <synthetic> | ||
public java.lang.Object Test$bar4$.g(java.lang.String) <bridge> <synthetic> | ||
public java.lang.Object Foo4.h(java.lang.Object) | ||
} | ||
|
||
class Test$bar5$ { | ||
public java.lang.String Test$bar5$.f(java.lang.String) | ||
public java.lang.Object Test$bar5$.f(java.lang.Object) <bridge> <synthetic> | ||
public java.lang.Object Test$bar5$.f(java.lang.String) <bridge> <synthetic> | ||
public java.lang.String Test$bar5$.f(java.lang.Object) <bridge> <synthetic> | ||
public java.lang.String Test$bar5$.g(java.lang.String) | ||
public java.lang.Object Test$bar5$.g(java.lang.Object) <bridge> <synthetic> | ||
public java.lang.Object Test$bar5$.g(java.lang.String) <bridge> <synthetic> | ||
public java.lang.String Test$bar5$.g(java.lang.Object) <bridge> <synthetic> | ||
public java.lang.Object Test$bar5$.h(java.lang.Object) | ||
} | ||
|
||
class Foo1$class { | ||
public static java.lang.String Foo1$class.f(Foo1,java.lang.Object) | ||
} | ||
|
||
class Foo2$class { | ||
public static java.lang.Object Foo2$class.f(Foo2,java.lang.String) | ||
} | ||
|
||
000000000000000000000000000000000000 |
Oops, something went wrong.
Yeah, I don't know about the truth of that. I could tell that was my phrasing but I didn't remember thinking it, so I dug up the commit from whence it was paraphrased: it's 3a1d34e .