You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AnnotatedTypes#adaptParameters is called after calls to constructorFromUse and methodFromUse.
The xFromUse methods should already return the signature of an executable element for that particular use.
The handling of synthetic constructor parameters is also inconsistent. If they are in the parameter list, we need to make sure there are corresponding arguments in invocations.
At the moment, these parameters are simply dropped from the parameter list, without checking that the types actually match.
In certain situations that is okay, e.g. for an anonymous constructor no explicit types can be provided.
But is it okay e.g. for an implicit outer this parameter? Shouldn't these be checked against the (implicit) argument?
The text was updated successfully, but these errors were encountered:
The adaptParameters calls are fixed by #406.
The enclosing receiver issue is fixed by #405.
For the handling of synthetic parameters, there is a new issue #400.
AnnotatedTypes#adaptParameters
is called after calls toconstructorFromUse
andmethodFromUse
.The
xFromUse
methods should already return the signature of an executable element for that particular use.The handling of synthetic constructor parameters is also inconsistent. If they are in the parameter list, we need to make sure there are corresponding arguments in invocations.
At the moment, these parameters are simply dropped from the parameter list, without checking that the types actually match.
In certain situations that is okay, e.g. for an anonymous constructor no explicit types can be provided.
But is it okay e.g. for an implicit outer this parameter? Shouldn't these be checked against the (implicit) argument?
The text was updated successfully, but these errors were encountered: