CallerMemberName and local methods

[FaustVX]

Why the compiler inserts the parent method identifier instead of the local method indentifier here ?

static class Program
{
    static void Main()
    {
        Print(); // will print Main
        Level(); // will also print Main
        
        static void Level()
            => Print();

        static void Print([CallerMemberName]string name = null!)
            => Console.WriteLine(name);
    }
}

sharplab.io

Of course, it works the same with top-level program, but will print <Main>$ instead.

[RikkiGibson]

I think the idea here is that local functions are not members and thus their names don't get used for CallerMemberName. Only the containing member's name gets used, i.e., Main.

Since the containing member will always be the same for all calls of a local function, the current behavior is perhaps not that useful.

[FaustVX]

Ok,
Is it possible to change that in a future version ? (or is this a breaking change ?)
To me, it's not the expected behavior, and like you said, it's not useful.

[CyrusNajmabadi]

Definitely a breaking change :-). I technically prefer the current behavior. Otherwise it's visible if your caller is a lambda vs local function, which I don't like.

[FaustVX]

Ah, I didn't think of that 😄