English text:Microsoft Reiterates its Support of F#
Microsoft's Mads, Torgersen, and Philip Carter (respectively, project managers at C# and F#) jointly released oneIntended to promote the use of F#Blog post. Post isBuild 2017 speech on F#Subsequent refinements are discussed in terms of how Microsoft removes barriers in adopting F#, and improvements in F# given in Visual Studio 2017
At the beginning of the article, Mads pointed out that they wanted to solve some of the people's ideas about adopting F# in this article. The two most common concerns they heard were:
Microsoft has been working on these issues last year. One action was launched by Microsoft.NET language strategyWhich points out the strong support for F#:
We will continue to provide the necessary supplement for the community contribution to construct the framework and tools, and to encourage the community to permit F# strong participation. By improving the experience of language and tools, make a contribution to the removal of obstacles, and solve the pain points in order to reduce the C# and VB between the experience gap, we will become the F# the function of language is the best tool on the market. Once the new language features in C#, we will ensure that these new features will interact with F# very well.
For the above mentioned in the adoption of F# in the second main obstacles, Microsoft is committed to the improvement in Visual is given in Studio 2017. An improved field is automatic function code, IDE the current proposal to open the module in the input function name.
Rename refactoring (Rename Refactoring) is a new feature and rename refactoring.F# Visual Studio is a Roslyn Workspace API the actual concrete results in the F# compiler. The Visual Studio is the same as the characteristics of the two languages, Workspace API abstract language specific implementation details.
The Carter member of the F# community work, all of their fields of F# are given, including the contribution of the compiler.F# community has also been described as a forerunner of Microsoft open source. For example, the F# compiler is open source in April 2014, a year prior to the C# compiler.
F# is suitable for applications such as cloud workloads. This direction is consistent with the development of Microsfot, which is to promote the cloud.Torgersen also pointed out that they see a lot of potential to grow. If possible, use a large number of users will love F#.
As part of the big goal of adopting F#, the document has been improved. Some of the introductory guidelines already include: