IssueRaiser

F# Status on CoreRT and UWP

**[2018-12-06 update] F# UWP apps can be released on the Windows Store.** https://github.com/dotnet/corert/issues/6055#issuecomment-421032358 --- Recent testing has assessed the compatibility of F# with CoreRT and .NET Native. Only minor issues have been found, which are easily worked around (see specific issues below). CoreRT issues can always be tracked and worked on here, and .NET Native issues can now also be tracked now that users can compile using it (See gatekeeper.xml section). This post is a documentation of the status of F# and CoreRT as requested by @dsyme. This post will be kept up to date. One purpose is to inform F# developers using CoreRT and .NET Native. The second purpose is to inform the request for allowing F# usage on the Windows Store, a 1 line change that may require approval. ## Testing CoreRT and .Net Native went through basic tests (the F# cheatsheet), and specific tests (tail calls and highly nested generics as recommended by @MichalStrehovsky, and some of the F# test suite). .Net Native was further tested in a production app using typical F# structures (a symbolic algebra engine using large discriminated union trees, standard usage of record types, reactive UI using Xamarin.Forms, SQLite). CoreRT is used by a number of F# users already. (@ChrisPritchard has written a number of games without encountering any issues.) ## Specific Issues | Issue | UWP (.Net Native) | CoreRT | Workaround | | ------------- | ------------- | ------------- | -----

Posted by charlesroddie on Jul 5, 2018, 11:42 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments

ux (SaaS)

F# Status on CoreRT and UWP

charlesroddieJul 5, 2018, 11:42 AM

**[2018-12-06 update] F# UWP apps can be released on the Windows Store.** https://github.com/dotnet/corert/issues/6055#issuecomment-421032358 --- Recent testing has assessed the compatibility of F# with CoreRT and .NET Native. Only minor issues have been found, which are easily worked around (see specific issues below). CoreRT issues can always be tracked and worked on here, and .NET Native issues can now also be tracked now that users can compile using it (See gatekeeper.xml section). This post is a documentation of the status of F# and CoreRT as requested by @dsyme. This post will be kept up to date. One purpose is to inform F# developers using CoreRT and .NET Native. The second purpose is to inform the request for allowing F# usage on the Windows Store, a 1 line change that may require approval. ## Testing CoreRT and .Net Native went through basic tests (the F# cheatsheet), and specific tests (tail calls and highly nested generics as recommended by @MichalStrehovsky, and some of the F# test suite). .Net Native was further tested in a production app using typical F# structures (a symbolic algebra engine using large discriminated union trees, standard usage of record types, reactive UI using Xamarin.Forms, SQLite). CoreRT is used by a number of F# users already. (@ChrisPritchard has written a number of games without encountering any issues.) ## Specific Issues | Issue | UWP (.Net Native) | CoreRT | Workaround | | ------------- | ------------- | ------------- | -----

Comments (0)

No comments yet. Start the discussion.

Comment on this issue