What's Easy in F# That's Hard in C#? [duplicate]

This question already has answers here: Closed 11 years ago.

Possible Duplicate:

In what areas might the use of F# be more appropriate than C#?

I'm anticipating giving a presentation at the local .Net user group about F#. 开发者_StackOverflow社区And I'm anticipating the "Why should I look into F#?" question from the audience. I know most of the stuff that can be done in F# can be done in C# too--so I'm looking for things that can be done easily in F# that are really hard to do in C# (e. g. pattern matching). And if there are already good answers to this question, please just link them in comments and I'll close this up. I did see a few things but if there's already a question that addresses this I didn't find it.

By the way, if any of the moderators want to mark this community wiki please feel free; this seems more like a survey question to me anyway.

---

Since F# is a functional language, it should be far easier to implement a domain-specific language in it.

---

One of a main concept is asyncrounus calls in F#, also F# uses immutable variables so concurrency is easy.

see http://research.microsoft.com/apps/pubs/default.aspx?id=147194 and http://research.microsoft.com/apps/pubs/default.aspx?id=79947 and other Don Syme articles. may be there are other differences, but I think gathering them here is just doing your homework.

---

i would say

• Asynchronous programming.
• Units of measure