Closed GoogleCodeExporter closed 9 years ago
I have made a fix, but I fear that it will not be sufficient in the long run,
as I think it misses a couple corner
cases. Namely, if we look through the list of interfaces/superclasses and
examine one that includes a method
that is acceptable under primitive widening and there is a separate interface
that better matches the signature,
we will call the wrong method. I will see if there is a relatively simple fix
for this problem.
Original comment by mhahn...@gmail.com
on 19 May 2010 at 7:23
I added a function requiresPrimitiveWidening() that checks whether a method and
the types of the parameters to
the passed to the method require primitive widening. I've modified
PlaidJavaMethodMap to incorporate the new
function and call the correct one accordingly.
Original comment by mhahn...@gmail.com
on 19 May 2010 at 8:33
Original issue reported on code.google.com by
mhahn...@gmail.com
on 18 May 2010 at 9:08