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
Always keep annotations on value parameters for class methods
The previous code always dropped annotations from all constructor parameters
and also from all parameters of derived methods such as copy and apply. That
last part was an error: there was code that meant to compensate for it, but
because of a typo the compensation code did nothing. The commit that dropped
parameters was b602d83 "Drop annotations from constructor parameters". That
commit had as motivation that cyclic references could be avoided by dropping
@specialized on type parameters. So by that logic it seems safe to keep annotations
on value parameters of constructors. This could be important if (say) we have an
annotation indicating default arguments, which certainly will have to be kept
on the constructor as well.
0 commit comments