F# team just posted an update on their GitHub. https://github.com/Microsoft/visualfsharp/issues/1096
This is still a work in progress. One key thing from that post is some of these features and fixes have already been underway for months. While we’ve been investigating F#-specific issues in .NET Native, the team has continued to improve .NET Native. One feature known as “universal shared generics” is likely to have improved .NET Native’s support for F#, even without that being an explicit goal of the feature.exercitus vir commented
Microsoft needs to realize that no one develops primarily for WinRT because the market share is so small. Instead, developers port their Android and iPhone apps to WinRT if it isn't too much trouble. Xamarin is what makes this possible, which does support F#. If you don't support F#, then you will simply lose even more market share.
And if you don't choose to support all and any .NET language, then you might want to rename .NET Native to C# Native or VB Native. Otherwise, that name is misleading.exercitus vir supported this idea ·