Change signature adds unnecessary argument names

Repository metrics

Stars

20,414 stars (20,414 stars)

PR merge metrics

Avg merge 6d 17h (Avg merge 6d 17h)256 merged PRs in 30d (256 merged PRs in 30d)

Description

class Program
{
    static void F(int a, int b, int c)
    {
    }

    static void Main()
    {
        F(1, b: 2, 3);
    }
}

class Program
{
    static void F(int b, int c, int a)
    {
    }

    static void Main()
    {
        F(b: 2, 3, 1);
    }
}

class Program
{
    static void F(int b, int c, int a)
    {
    }

    static void Main()
    {
        F(b: 2, c: 3, a: 1);
    }
}

Contributor guide

Research direction

Inspect the ChangeSignature refactoring code, specifically the part that decides which arguments to render with named arguments at the call site. Look for logic that adds argument names even when not necessary, as in the case of moving a parameter that originally had a named argument after changing the signature order.

Tech stack

csharp

Domain

developer experience

Issue type

Bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-2 days

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

C#Git

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

70