Imported From: https://issues.scala-lang.org/browse/SI-6043?orig=1
Reporter: @gkossakowski
See #8247, #5005

@paulp said:
"This problem is caused by the fact that AnyRef specialization is a bit more tricky than specialization on primitive types. When we specialize on AnyRef and then we check if given type argument for specialized type parameter is valid we have to use subtyping relationship instead of equality."

Are you sure of this assessment? This looks more to me like a case of comparing types in the wrong environment. In Baz, A=String, and def apply(x: String): Boolean exists. When looking for specialized overrides involving A, (String)Boolean is exactly the method signature it ought to be looking for. The fact that it doesn't override it says to me it's looking for the wrong signature, not that it needs to apply a different test.

Parameter types of method overrides must match exactly, which also makes me skeptical that a subtype test is what's needed.

@adriaanm said:
Please re-assign to Vlad if that's more appropriate.

@axel22 said:
This is my pending fix for that one:

axel22/scala-github@830ba25

but I still have to test it, and right now I have my hands full with @static.

@non said (edited on Aug 14, 2012 4:37:49 AM UTC):
One comment on this bug: it's well-known that specialization doesn't work with class-inheritance (it's described in the paper and also in some of the docs). Thus, I don't think this example would ever work.

If you change Inter into a trait, you'll see specialization occuring:

public class Baz extends java.lang.Object implements Inter{
    public boolean apply$mcI$sp(int);
    public boolean apply(java.lang.String);
    public boolean apply(java.lang.Object);
    public Baz();
}

That said, AnyRef specialization is currently turned off, so the only specialization available is apply$mcI$sp but I think the point still stands.

I only checked this bug because I'm trying to go through and close old specialization bugs that might now be fixed in master.