F# to become 1st class .NET language

home
clr
view story

21 Kicks

F# to become 1st class .NET language(blogs.msdn.com)

submitted by JudahGabriel(783) 4 years, 3 months ago

F#, the functional programming language born from ML and incubated by Microsoft Research,, is ready for prime time. Full Visual Studio support, a commercial development team, official support, the whole bit. F# becomes the first functional language to get 1st class support on the CLR.

5 comments |category: CLR |Views: 19
Tweet

tags: F# CLR another

Everyones tags:

Your Tags:

Please login or signup.

Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

"Kick It" text
"Kick It" background
kick count text
kick count background
border

Simply copy and paste this HTML into your blog post.

Users who kicked this story:

jdh30(245) -

ashithmr(90) -

Loonquawl(0) -

BlackWasp(4024)

More who kicked this story...

Comments:

posted by atifaziz(1000) 4 years, 3 months ago 0

Wish they'd give IronPython a bit of the same love, which has been in release since a while now. It would be sweet to get fully-supported Visual Studio integration. It is there as an integration sample as part of the VS 2005 SDK, but then again, it's just a sample (albeit an impressive one).

posted by JudahGabriel(783) 4 years, 3 months ago 0

Yes, I'd like to see IronPython and, when ready, IronRuby get the same 1st class .NET citizen treatment.

posted by ashmind(775) 4 years, 3 months ago 0

Now what's missing is the ability to write a part of a partial class in F# and a part in C#.
Or, at least, an ability to keep different language classes in the same project.

posted by JudahGabriel(783) 4 years, 3 months ago 0

I don't think the "different language code files in same project" is a good idea. I think we'd see some bad abuses of that; a whole project should be of one language, IMO.

posted by ashmind(775) 4 years, 3 months ago 0

Following your point, why not a whole solution in single laguage?

There are often XML, XSLT, ASP.NET markup, Javascript, CSS and C# living together in the same project.
And things like Regular Expressions live happily even inside the C# code.
Also, the projects themselves are MSBuild.

Does it really makes everything harder to understand?
I doubt that Xml transform in C# (without XLinq) is more understandable than Xslt.
And if I write Xml transformation in Xslt, isn't it better to write tree walking in F# active patterns?

Most Active Users

What's this?