137 votes4 comments · Universal Windows Platform » XAML/Controls/Composition · Flag idea as inappropriate… · Admin →AlexKven commented
Definitely want this. I have an app that would make use of this.
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.AlexKven commented
I have a UWP app in the Win 10 store right now, and there is a component I'm thinking about implementing. It is functional in nature, and I would do it in F# in a second if I could. In fact, it would be fairly painless to do it in F# even though it would have to be in a separate library.
Furthermore, I have an app in the Windows 8 store (2048 Sandbox) that actually uses F# for a large part of the game board UI (it's actually one of the 0.01%). I would not be able to port that app to Windows 10 UWP without some serious rewriting of F# code in C#.
5 votesAlexKven shared this idea ·