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
I love F# but after seeing where MS is heading (and reading all these comments didn't help either) I am too afraid to invest more time and effort into F#. What I am afraid of is that MS will drop it like it did with Silverlight but the whole situation is more like what happened to the DLR and its languages like IronPython. The one thing they have learned from the Silverlight case is that instead of publicly announce a death sentence of a tech it is better to silently abandon it and let it wither away.
What was the point of publishing F# and not giving it the tooling support it needs to prosper? MS is alienating more and more developers.