Cannot P/Invoke a function named "Process()"

Steps to reproduce

Define the following function in C and compile as a DLL:

__declspec(dllexport) int Process()
{
    return 42;
}

Run the following in PowerShell with the path to the DLL in the DllImport:

$type=Add-Type -MemberDefinition @'
[DllImport("C:\\PathToRepro.dll")]
public static extern int Process();
'@ -Name TestProcess -PassThru

$type::Process()

Expected behavior

Function returns 42.

Actual behavior

The following error occurs: The result type 'System.Int32' of the dynamic binding produced by the object with type 'System.Management.Automation.PSObject' for the binder 'PSInvokeMember: static Process ver:0 args:0 constraints:<>' is not compatible with the result type 'System.Object' expected by the call site.

Changing the name of the function to something else such as Process2() works as expected.

I was not able to reproduce this when using a C# program instead of PowerShell.

Environment data

Name                           Value
----                           -----
PSVersion                      7.1.0
PSEdition                      Core
GitCommitId                    7.1.0
OS                             Microsoft Windows 10.0.20231
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

[SeeminglyScience]

Oh also probably a better repro:

class Test {
    static [int] Process() {
        return 10
    }
}

[Test]::Process()

[SeeminglyScience]

Looks like it’s any static method named either Process, or End (incidentally, not Begin because it has a void return) without arguments that returns a value type.

Easier repro:

Add-Type -TypeDefinition 'public class Test { public static int Process() => 10; }'
[Test]::Process()

I would guess that it’s caused by the special casing here:

https://github.com/PowerShell/PowerShell/blob/db94377b3a69511280d329e64375475f6d7513b8/src/System.Management.Automation/engine/runtime/Binding/Binders.cs#L6915-L6927

It’s not immediately obvious how that’s happening, but it sure seems like it is.

/cc @daxian-dbw you might find this interesting. Looks like the binder is somehow returning true here and exiting early, skipping the cast to object right afterwards.