cloudroutine
Joined 12 years ago
Karma
38
Submissions
11
Member since
Jun 29
Recent submissions
Comment · 10 years ago
it is for atom, not yet for vscode
Comment · 10 years ago
Considering the two existing ways to defines structs are
type S = struct val X:int end
type [<Struct>] R = val Y:int
The examples in the blog post aren't in accordance with the RFC as far as type signatures are concerned [1] The tuple decomposition is mixed in with the type sig.
let getPointFromOffset (point: struct (x, y)) (offset: struct (dx, dy)) = ...
let getPointFromOffset (struct(x, y) as point) (struct (dx, dy) as offset) = ...
let getPointFromOffset ((x, y): struct(int * int)) ((dx, dy): struct(int * int)) = ...
[1] https://github.com/fsharp/FSharpLangDesign/blob/master/RFCs/...
Comment · 11 years ago
FunScript is in the middle of a restructuring/reorganization process[1]. Hopefully FunScript will find its legs and start moving forward sometime soon.
Intellifactory's Websharper projects are well supported and regularly updated, you could try Websharper.Warp[2] in lieu of FunScript.
Comment · 11 years ago
I started out with OCaml too, it's a really easy transition into F#. You can basically cut and paste OCaml code into F#, unless it involves stuff like Functors, first class modules, and polymorphic variants.
Active Patterns are a pretty cool F# feature that OCaml doesn't have. You can do something that's effectively the same with OCaml macros, but those are a lot more tedious.
The F# intellisense and code completion are great productivity enhancers, especially when it comes to working with unfamiliar libraries.
My biggest hurdle in transitioning from OCaml to F# was learning my way around the .Net ecosystem, so it was still a relatively minor one.
If you decide to get into F# and have any questions about it someone on the #fsharp channel on the Functional Programming Slack[1] usually has an answer.
[1] http://fpchat.com/ <- sign up here, invites usually arrive within 24hrs
Comment · 11 years ago
Could you try updating the `ionide-installer` plugin? We had some minor issues over the past 30 mins[1] but they should be resolved now.
We definitely support Windows, I'm running it on Windows 10 right now ;)
Comment · 11 years ago
That was Omnisharp-Server, they only switched over to the Omnisharp-Roslyn[1] implementation a few months ago.
Comment · 11 years ago
VS Code does not currently support extensions/plugins. The team has confirmed they're coming at some point[1] but we'll need to see how they set it up to determine the best approach to building an F# plugin for it.
Ionide definitely won't be compatible out the gate, but if the API isn't too different we might be able to reuse some of what we've already done.
The best case scenario would be the if plugin system supports dlls so that we could use the FSharp.Compiler.Service directly[2]
[1] http://visualstudio.uservoice.com/forums/293070-visual-studi...
Comment · 11 years ago
It's not Omnisharp, we use FsAutocomplete[1] which is essentially a wrapper around the FSharp.Compiler.Service[2]
Comment · 11 years ago
You should also install the F# Power Tools[1] if you haven't already. It has a lot of great features.
I definitely prefer Atom+Ionide when I want to try something out quickly or experiment. Opening VS and creating a new project just to write a simple fsx script seems excessive to me.
Although, most of the time I'm running them simultaneously.