I found this in a blog: “What does this C# code look like in F#? (part one: expressions and statements)” C# has an operator called “default” that returns the zero-initialization value of a given type: default(int) It has limited utility; most commonly you may use default(T) in a generic. F# has a similar construct as … Read more
I think your summary for when to choose Seq is pretty good. Here are some additional points: Use Seq by default when writing functions, because then they work with any .NET collection Use Seq if you need advanced functions like Seq.windowed or Seq.pairwise I think choosing Seq by default is the best option, so when … Read more
I can only support what gradbot said – when I need mutation, I prefer let mutable. Regarding the implementation and differences between the two – ref cells are essentially implemented by a very simple record that contains a mutable record field. You could write them easily yourself: type ref<‘T> = // ‘ { mutable value … Read more
See danielnixon’s answer for the official way to do this now. It is possible. 1. Your project needs to work on Mono On your own mono machine, using the terminal, cd into your solution directory and running the command xbuild. This may automatically work, or it may not, as there are features you used in … Read more
That is LINQ’s Select – i.e. var newSequence = originalSequence.Select(x => {translation}); or var newSequence = from x in originalSequence select {translation};
General benefits of functional programming over imperative languages: You can formulate many problems much easier, closer to their definition and more concise in a functional programming language like F# and your code is less error-prone (immutability, more powerful type system, intuitive recurive algorithms). You can code what you mean instead of what the computer wants … Read more
So the kind of a type is its simple type. For instance Int has kind * which means it’s a base type and can be instantiated by values. By some loose definition of higher-kinded type (and I’m not sure where F# draws the line, so let’s just include it) polymorphic containers are a great example … Read more
A namespace is a .Net thing, common in many industrial-strength languages, just a way to organize frameworks and avoid naming conflicts among different libraries. Both you and I can define a type “Foo” and use them both in a project, provided they are in different namespaces (e.g. NS1.Foo and NS2.Foo). Namespaces in .Net contain types. … Read more
It seems like the book Real World Haskell is just what you’re looking for. You can read it free online: http://book.realworldhaskell.org/
A couple of thoughts here since there isn’t much online and this project is on hiatus apparently with likely no support for Mono compatibility coming anytime soon. 1) Not sure what version or build you have of Gallio, but you may try the Gallio bundle nuget from here and see if you get different results … Read more