Some quick F# notes…
Posted by Brian on November 1, 2009
I am lining up a blog series, but in the meantime, here are a few quick notes and links to keep you occupied. :)
First, I forgot to mention that the documentation for the F# runtime (FSharp.Core.dll) is now online on MSDN. Previously these docs were only available from the F# website on research.microsoft.com. The F# docs keep getting better and better, as well as more fleshed out (and I really like the new look and improved usability of the MSDN site overall). So: don’t forget the docs, they’re a valuable resource.
For those of you just getting started with F#, here’s a summary of my most useful introductory/reference links:
- Brian’s favorite online content for learning F# – a summary of good links to docs/videos/etc
- A three-part overview of the syntax of the language:
- The basic syntax of F# – keywords and constructs
- The basic syntax of F# – classes, interfaces, and members
- The basic syntax of F# – types
- What does this C# code look like in F#? – a comparative “here is some C#, here is the corresponding F#” reference
- F# function types: fun with tuples and currying – overview of tuples, curried functions, and partial application
- Pipelining in F# – a discussion on the pipeline operator (|>)
Teaser: Regarding what’s coming up, I intend to do a blog series about a little app I wrote that I find useful. It is a nice example that emphasizes the connectedness of F# with the rest of the .Net platform, in that the app uses F# (including some advanced features like async and MailboxProcessors) along with a variety of other technologies: WPF, IObservables, SyndicationFeeds, Speech APIs, SynchronizationContexts, and COM interop. To do something useful! (This is not just another “calculate factorials” example!) All in just 500 lines of code. So that will be fun to discuss; I’m looking forward to writing it up.
Please keep sending your feedback to the F# team! Since the Beta2 release we’ve received lots of useful feedback and bug reports. Keep it coming! We’re glad to hear from you at email@example.com.
Until next time…