The new TimeSpan FromMilliseconds overload breaks System.Linq.Expressions

[Tragetaschen]

Description

I have seen the breaking change notice with regards to F#, but migrating to .NET 9 has revealed a couple of places in our C# projects, where constructing a TimeSpan is part of a System.Linq.Expressions.Expression. These now don't compile with .NET 9

Reproduction Steps

using System.Linq.Expressions;
Expression<Action> a = () => TimeSpan.FromMilliseconds(1000); // compiles with .NET 8, fails with .NET 9

Expected behavior

Code continues to compile

Actual behavior

Code breaks in .NET 9

Regression?

yes

Known Workarounds

You need to force the double overload

Expression<Action> a = () => TimeSpan.FromMilliseconds(1000.0);

or provide the optional parameter

Expression<Action> a = () => TimeSpan.FromMilliseconds(1000, 0); 

Configuration

No response

Other information

The reason is that the optional parameters are not supported in expressions.

[dotnet-policy-service]

Tagging subscribers to this area: @cston
See info in area-owners.md if you want to be subscribed.

[Tragetaschen]

Introduced with #93890

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-datetime
See info in area-owners.md if you want to be subscribed.

[dotnet-policy-service]

Tagging subscribers to this area: @cston
See info in area-owners.md if you want to be subscribed.

[julealgon]

I was under the impression that exposing methods with default parameters in public APIs was frowned upon, and that it was best to just have multiple overloads instead.

Does anybody know if that's not really the case, or if it still applies, why these new APIs for TimeSpan didn't follow that practice?

[Tragetaschen]

The approved API said

The methods should be overloaded to have no default parameters per our normal default parameters usability guideline

But the actual API missed the milliseconds overload and consequently didn't implement it in #98633.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-datetime
See info in area-owners.md if you want to be subscribed.

[tarekgh]

Just to mention the other workaround can be providing the optional parameter:

Expression<Action> a = () => TimeSpan.FromMilliseconds(1000, 0); 

Thanks @Tragetaschen for reporting the issue.