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.Anonymous commented
"Low historical usage of the language" is a false statement when considering F# is relatively a new language and the lack of tooling support for it. What would anyone expect?
I don't think decision makers on this are aware of the advantages of F# over C# With F# we can turn ideas to prototypes and working apps way faster than C# and with less resources. This means more apps entering to windows store frequently. MS should invest more to F#.Anonymous commented
I spent 6 years with c#, spent a year with f# and I do not want to go back. Please supportAnonymous supported this idea ·