The name of a parameter in an externally visible. This rule raises an issue when method override does not match the name of the parameter in the base declaration of the method, or the name of the parameter in the interface declaration of the method or the name of any other ``++partial++`` definition.
\[~evgeny.mandrikov] note that this seemed familiar to me, but I couldn't find a relevant C-Family rule.
=== on 13 May 2015, 21:03:05 Evgeny Mandrikov wrote:
\[~ann.campbell.2] I suppose that you have in mind RSPEC-927
=== on 14 May 2015, 11:12:14 Ann Campbell wrote:
Thanks [~evgeny.mandrikov]
=== on 22 May 2015, 09:44:25 Tamas Vajk wrote:
Could you run through it one more time? There were minor modifications in the sample code.
=== on 22 May 2015, 12:14:06 Ann Campbell wrote:
\[~tamas.vajk] I'm not sure why you swapped the parameter order. I feel like reversing the names is a better illustration of the confusion that could result in param names that don't match...?
=== on 22 May 2015, 12:48:42 Tamas Vajk wrote:
\[~ann.campbell.2] I changed it because ``++yk++`` was not used in the method body, so it already just looked like a typo.