由网友(风吹誓言.)分享简介：我无法放置被引入F＃语言的概念和possiblities来自微软。I'm having trouble placing the concepts and possiblities of the to be introduced F# language from Microsoft.威尔F＃中使用只是为了声明函数？或者...

我无法放置被引入F＃语言的概念和possiblities来自微软。

I'm having trouble placing the concepts and possiblities of the to be introduced F# language from Microsoft.

威尔F＃中使用只是为了声明函数？或者将应用在F＃编写的完全混合F＃与普通的C＃或VB code？

推荐答案

我的期望是，F＃将用于的片的一些专门的系统 - 这涉及复杂的线程/数学/财务比特/建模/等，其中F＃做得很好。对于大多数其他地区（用户界面，DAL等），通用的语言，如C＃似乎（IMO）preferable。

My expectation is that F# will be used for pieces of some specialized systems - the bits that involve complex threading / maths / financial / modelling / etc, where F# does well. For most other areas (UI, DAL, etc), a general purpose language like C# seems (IMO) preferable.

之一的F＃的优点是（理论上），你可以的证明的code是工作，而不仅仅是测试它。该线程支持（感谢不变性和异步！用法）也不错（虽然PLINQ可能竞争线程）。

One of the advantages of the F# is that (in theory) you can prove code is working, rather than just test it. The threading support (thanks to immutability and the async ! usage) is also good (although PLINQ may compete on threading).

挂钩到.NET允许F＃，C＃，VB，IronPython的，IronRuby的，等之间的适当整合 - 真正显示出各的长处。 今天的，如果我是做大量的COM互操作的，我会考虑VB（这将在4.0更改与动态）;对于大多数code - C＃。对于数学等，F＃。整洁。

Hooking into .NET to allow proper integration between F#, C#, VB, IronPython, IronRuby, etc - really shows the strengths of each. Today if I was doing lots of COM interop, I'd consider VB (that'll change in 4.0 with dynamic); for most code - C#. For math etc, F#. Tidy.