Tracking Issue for C# 11.0 Interop for F# 6.1/7.0

Okay we need an issue to track F# language updates for the next release.

The target is to release by Fall 2022 — so it’s going to be a small set of features, this is not an ordered or prioritized list

Feel free to discuss and add suggestions here in this thread.

1. Support for consuming Interface Static Methods - C# 10.0 feature
2. Required property/field: C# 11.0 feature
3. Ref fields C# 11.0 feature
4. User defined check operator [C# 11.0 feature] (https://github.com/dotnet/csharplang/blob/main/proposals/checked-user-defined-operators.md?rgh-link-date=2022-02-10T19%3A05%3A24Z)
5. Relaxing shift operator signature requirements - C# 11.0 feature
6. Unsigned right shift operator (>>>). C# 11.0 feature
7. https://github.com/dotnet/fsharp/issues/8654
8. Support CompilerFeatureRequiredAttribute, more info.

Background: we believe we need to do a good job supporting this style: https://docs.microsoft.com/en-us/dotnet/csharp/whats-new/tutorials/static-abstract-interface-methods

/cc @dsyme , @KathleenDollard , @jonsequitur , @vzarytovskii , @baronfel

[KathleenDollard]

I want to add one that is .NET 7, rather than C#, but it is driven by .NET, so may belong on this list: trimmability of FSharp.Core. I would hate to see F# cut out of Native AOT.

Other than that, 2 (required) also includes respect for init scope. I would have to put that first because we do the wrong thing (ignoring an expected contract) rather than just not being able to consume. But statics are such an important feature that if we cannot do these two things, I will definitely cry.

[cartermp]

Agreed @KathleenDollard, F# should be a part of the AOT story with no more caveats that C# (within reason!)