[Arguments(decimal, decimal)] does not infer correct type since v0.50.0

[AlexandreBossard]

    [Test]
    [Arguments(2_000, 123_999.00000000000000001)]
    [Arguments(2_000.00000000000000001, 123_999)]
    [Arguments(2_000.00000000000000001, 123_999.00000000000000001)]
    public async Task Transfer(decimal debit, decimal credit)
{
        Console.WriteLine("{0} {1}", debit, credit);
}

prints

2000 123999
2000 123999
2000 123999

which is incorrect :-)

And I can confirm the value in the debugger.

I tried casting to decimal and using the M suffix literal, but it does not compile.

[BramMusters]

I think this is a similar issue:

    [Test]
    [Arguments(0.5)]
    [Arguments(0.75)]
    [Arguments(1)]
    public void Test(decimal test)
    {
        return;
    }

The second and third tests fail with Expected exactly 1 argument, but got 2

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.

[thomhurst]

@AlexandreBossard @BramMusters this should be fixed in the latest version

[AlexandreBossard]

I'm sorry, but it still does not work. I've updated to v0.61.39.0 and unskipped the exact same test, still fails.

[thomhurst]

Roslyn automatically picks up the constant value as a double, so it might be losing precision there.

Try using a string argument instead - does that work?

[AlexandreBossard]

Using strings and keeping the decimal arguments, doesn't work, unsurprisingly. I can use strings all the way down and do a "decimal.Parse()but that kind of defeat the point. Also it used to work before0.50.0`.