Bug 9712 - Poor F# support
Summary: Poor F# support
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.8.x
Hardware: PC Mac OS
: High normal
Target Milestone: ---
Assignee: Atsushi Eno
Depends on:
Reported: 2013-01-22 12:52 UTC by Andrew Pennebaker
Modified: 2013-05-23 13:30 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Andrew Pennebaker 2013-01-22 12:52:18 UTC
F# is only supported as a hack, requiring compilation to JavaScript and then running on a rather limited WebKit environment. Can we add better F# support to Mono for Android?
Comment 1 Gonz 2013-03-12 19:08:06 UTC
Could we also get a Z-machine front end with triglyphs and full localization for Esperanto?  My totally existent professional app can't ship without it!
Comment 2 Jonathan Pryor 2013-05-22 16:11:21 UTC
Is this fixed in 4.7.x/master?
Comment 3 Atsushi Eno 2013-05-23 13:30:04 UTC
Now that asm.js is supported there is no problem to first translate F# into Javascript then WebKit will automatically translate them into native code. Win!

(No, actually F# support in our Xamarin.Android runtime is in our 4.7.x release, with some fixes on Windows side in the next alpha release ;-)