Fix TimeSpan.FromMilliseconds ambiguity with .NET 10
#547
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When trying to build for .NET 10, I'm getting
The reason is that in .NET 9.0 TimeSpan.FromMilliseconds had 2 overloads:
In .NET 10.0 there are now 3 overloads:
... and F# doesn't know whether it should convert the provided int32 into an int64 or double.
This patch defaults to double which makes it compile with both .NET 9 and 10.