Seattle F# meetup, Wednesday 7/17/2013, 7:00 PM: Functional-style control flow in F#

Seattle F# meetup, Wednesday 7/17/2013, 7:00 PM: Functional-style control flow in F#

  • Comments 2

Join the F# Seattle User Group meetup next Wednesday for a talk about functional-style control flow in F#:

Many developers come to F# from the imperative world of C#, where they are accustomed to various loop types, if/else blocks, switches, breaks, and other imperative control flow mechanisms.  Some of these concepts are simply not present in F#, and those that are often translate into awkward, verbose F# code.

In this meetup we will discuss a better approach: Using idiomatic, functional-style control flow in your F# code.  We'll look at various items in the functional toolbox, including pattern-matching, recursion, and higher-order functions, and see how they can make your code more readable and concise.

Presented By: Lincoln Atkinson

When: 7/17/2013, 7:00 PM

Where: Microsoft Building 32, 3620 163rd Avenue Northeast, Redmond, WA

More details: http://www.meetup.com/FSharpSeattle/events/128782742/

Leave a Comment
  • Please add 7 and 2 and type the answer here:
  • Post
  • Hello, I am new to F#.

    I opened http://www.tryfsharp.org/ in Internet Explorer 11 on Windows 8.1.

    I get the following error:

    "Welcome to Try F#! Your system does not support the execution of F# code in the browser.

    You can still read the tutorials and view code in the editor. Please see the Explore section for other ways to run F# code.

    For additional help about this site: www.tryfsharp.org/Help"

    Can you please fix it for future versions of Internet Explorer.

  • Hello, I opened www.tryfsharp.org/ in Internet Explorer 11 on Windows 8.1.

    I get the following error:

    "Welcome to Try F#! Your system does not support the execution of F# code in the browser.

    You can still read the tutorials and view code in the editor. Please see the Explore section for other ways to run F# code."

    It worked fine on IE10.

    Can you please fix it for future versions of Internet Explorer.

Page 1 of 1 (2 items)