[Mono] Fix ParameterInfo.Name to return null for unnamed parameters

[medhatiwari]

[Mono] Fix ParameterInfo.Name to return null for unnamed parameters

Summary

Fixes runtime inconsistency where Mono's ParameterInfo.Name returns empty string ("") for unnamed parameters while CoreCLR correctly returns null.

Problem

Failing Tests:

• OpenApiOperationGeneratorTests.ThrowsInvalidOperationExceptionGivenUnnamedParameter
• RequestDelegateFactoryTests.CreateThrowsInvalidOperationExceptionGivenUnnamedArgument

Root Cause:

// CoreCLR behavior (correct)
var param = lambda.Compile().Method.GetParameters()[0];
param.Name == null  // true

// Mono behavior (bug)
param.Name == ""    //  empty string, not null

ASP.NET Core validation checks if (parameter.Name is null) - this works on CoreCLR but fails on Mono.

Reproduction

using System;
using System.Linq.Expressions;

var unnamed = Expression.Parameter(typeof(int));
var lambda = Expression.Lambda(Expression.Block(), unnamed);
var param = lambda.Compile().Method.GetParameters()[0];

// CoreCLR: param.Name is null 
// Mono: param.Name is "" 
Console.WriteLine($"Name is null: {param.Name is null}");

Test Results:

• With only loader.c fix: param.Name still returns ""
• With both fixes: param.Name correctly returns null

Why

ParameterInfo.Name is nullable (string?) per API Contract)

Related Issues

Fixes failures in dotnet/aspnetcore test suite when running on Mono runtime.

cc: @giritrivedi

[BrzVlad]

mono_method_get_param_names_internal is called by a couple of other methods. We need to make sure that each of them expects and handles NULL value. This seems to produce quite a few crashes on CI, primarily around aot compilation, but it looks like debugger could also suffer.

[medhatiwari]

@BrzVlad Thank you for catching this! I've audited all callers of mono_method_get_param_names_internal and found 2 unsafe callers
debugger-agent.c:9327 - Added NULL check: names[i] ? names[i] : ""
dwarfwriter.c:1868 - Added NULL check: !pname || pname[0] == '\0'

and other callers (mini-llvm.c (lines 4168, 13298) - checks if (names[i]), debug-mini.c:680 - uses ternary names[i] ? names[i] : "unknown name"

already loosk safe
Please let me know if I'm missing something here or if there are other callers I should check.