Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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
GitHub or Developer Community 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.
Hi there. https://github.com/fsharp/fsharp/issues/784
It seems like the fsharp community cares sometimes less about such issues, like when distros use a current OpenSSL.
I suggest to support it as a part of this wonderful project, since F# is often a bit of an underrated language;
I'm not sure what F# has to do with Visual Basic (where you filed the bug)?
In any case this sounds like something you need to take up with the F# team/community.
There is no other category, to drop this in. This issue here is about F# support in MONO.