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.
Thanks deeply for those who supported this idea and those who remained open to it on the other. This is how even a big company like Microsoft can stay ahead of the curve!
Congratulations all around!
In this article, I try to make the case for .NET Native support for F# more generally -
Whether or not that's crucial to include support in UWP, I'm not quite as clear on. Couldn't hurt, I guess :)
I absolutely need this for Nu Game Engine, the world's first practical, pure functional game engine in F# - https://github.com/bryanedds/FPWorks
While the game engine is already reasonably fast, there's no reason it should be bottlenecked by the JIT, or to have be an even more significant resource drain on mobile. Not to mention start-up times!