Why are parameter names necessary in an interface definition? I am allowed to choose new parameter names during implementation
<p>Not sure if this is a silly question, but I just noticed this:</p>

<pre><code>public interface IActivityDao : IDao&lt;Activity&gt;
{
    IList&lt;Activity&gt; GetAllSinceSequence(long sequence, int count);
}

public class ActivityDao : AbstractNHibernateDao&lt;Core.Domain.Activity&gt;, IActivityDao
{        
    public IList&lt;Activity&gt; GetAllSinceSequence(long sequence, int maxRecords)
    {

    }
}
</code></pre>

<p>Inside of my implementation I have called my second parameter 'maxRecords.' Yet, in the interface, it is defined as 'count.' The compiler still consider the interface implemented, which is good, but can lead to a bit of ambiguity. Clearly, I should rename one of the parameters to match the other.</p>

<p>I played around a bit before making the rename and noticed something interesting. I'm not allowed to declare my interface as:</p>

<pre><code>public interface IActivityDao : IDao&lt;Activity&gt;
{
    IList&lt;Activity&gt; GetAllSinceSequence(long, int);
}
</code></pre>

<p>Is this just the compiler being overly protective against C# symantics? What purpose do the parameter names in an interface's method serve other than to make the code more readable? It seems to me that it invites ambiguity if the parameter names aren't forced upon implementations.</p>
