Don Syme

Hi @Andrew-Webb, I agree this is a significant problem - we need a clear position on this issue and we need that to be mapped through to fixes in the...

Thanks @Andrew-Webb, this is a very useful contribution. We'd be grateful if you could submit a PR to https://github.com/fsharp/fsharp.github.io/blob/master/_posts/2014-09-19-fsharp-libraries.md to add this as a specific recommendation. We can discuss the...

Duplicate of #886. REsolution is "use a regular record type"

The need for the use of function pointers in F# programming is vanishingly rare and the implementation cost quite high. I'll close this as "no" - however thank you for...

@smoothdeveloper I'll take another look. However my gut feeling has always been that this particular emulation of C in F# is just too much - and also an unpleasant sinkhole...

@T-Gro @vzarytovskii Do you have thoughts here? Personally I find the thought of putting such a primitive into F# really problematic - I just think it will lead far too...

I'm wondering about a compiler-known intrinsic that can be used like this: ```fsharp NativePtr.calli _pfn (xlFn, length, NativePtr.toNativeInt pFnParams, NativePtr.toNativeInt &&resp) ``` Not sure about the `Unmanaged`/`Stdcall`/`Thiscall`/`Fastcall` matrix - could...

If something like that would do the job then yes, approve-in-principle.

Now we need an implementation :) RFC is here: https://github.com/fsharp/fslang-design/blob/main/RFCs/FS-1128-allow-static-members-in-interfaces.md

Closing this as the remaining work isn't particularly significant and can easily be added as helpers