From: "Jon Harrop" <jon@ffconsultancy.com>
To: "'Paolo Donadeo'" <p.donadeo@gmail.com>,
"'OCaml mailing list'" <caml-list@inria.fr>
Subject: RE: [Caml-list] IDE
Date: Tue, 17 Sep 2013 21:36:31 +0100 [thread overview]
Message-ID: <036001ceb3e5$98c91240$ca5b36c0$@ffconsultancy.com> (raw)
In-Reply-To: <CAPzAKVCQuG=scc1jcEG946eSoAGuEa5VgupohEUabO4qUuvp6w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
Sure. Although Xamarin have announced that they intend to support F# as a first-class language on their toolstack they are still relying on the community-driven fsharpbindings. Xamarin recently put out an autoupdate to Xamarin Studio and several people including myself noticed that it broke F# support. No more “jump to definition” and some flakey Intellisense. I think the fix went into fsharpbindings on Github but I’ve no idea how long it will take to filter back to me.
So it isn’t all plain sailing but it is very impressive, IMO.
Cheers,
Jon.
From: caml-list-request@inria.fr [mailto:caml-list-request@inria.fr] On Behalf Of Paolo Donadeo
Sent: 17 September 2013 15:42
To: OCaml mailing list
Subject: Re: [Caml-list] IDE
Jon, can you explain the "when" part?
--
Paolo
[-- Attachment #2: Type: text/html, Size: 4003 bytes --]
next prev parent reply other threads:[~2013-09-17 20:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 6:34 Suminda Dharmasena
2013-09-08 12:41 ` Kristopher Micinski
2013-09-08 12:43 ` Michael Hicks
[not found] ` <1378644250512.324564603@boxbe>
2013-09-08 16:06 ` Suminda Dharmasena
2013-09-08 16:24 ` Daniel Bünzli
2013-09-09 15:09 ` Jon Harrop
2013-09-09 16:52 ` Suminda Dharmasena
2013-09-15 15:16 ` Hongbo Zhang
2013-09-15 20:22 ` Komtanoo Pinpimai
2013-09-17 11:20 ` Jon Harrop
2013-09-17 14:42 ` Paolo Donadeo
2013-09-17 20:36 ` Jon Harrop [this message]
2013-09-08 16:56 ` Thomas Refis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='036001ceb3e5$98c91240$ca5b36c0$@ffconsultancy.com' \
--to=jon@ffconsultancy.com \
--cc=caml-list@inria.fr \
--cc=p.donadeo@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).