What does this F# code look like in Erlang – Part 3 of N

Yan Cui

I help clients go faster for less using serverless technologies.

Related Posts

 

Throwing Exceptions

In F#, you can define a custom exception type by creating a type that inherit from System.Exception or using the lightweight exception syntax to define them with the same syntax as discriminated unions.

You can throw exceptions in F# using the raise keyword or using failwith or failwithf:

exception MyExceptionA

exception MyExceptionB of string

let exThrower (isA : bool option) =

    match isA with

    | Some(true) -> raise MyExceptionA

    | Some(false) -> raise <| MyExceptionB("Blah Blah")

    | _ -> raise <| new System.Exception()

    | _ -> failwith "Not a valid input"

Erlang also has a number of different exception types, the most common ways to raise an exception in Erlang is via:

  • error(Reason) – terminates the current process and includes a stack trace.
  • exit(Reason) – similar to errors, but does not return the stack trace.
  • throw(Reason) – throws exceptions that the caller can be expected to handle, also used as a way to return from deep recursion.

1> throw("Blah Blah").

** exception throw: "Blah Blah"

2> error(boo).

** exception error: boo

3> exit(foo).

** exception exit: foo

 

Catching Exceptions

In F#, you can implement a try-catch block using the try-with keywords, and it’s really easy to use pattern matching to make handling multiple types of exceptions really easy.

Borrowing from the wonderfully humorous example from Learn you some Erlang for great good! here’s how it’ll look in F#:

 

In Erlang, the syntax is surprisingly similar:

 

Another thing to keep in mind is that whilst F# has try-with and try-finally blocks there is no equivalent of C#’s try-catch-finally block. In Erlang the try-catch-finally block looks like this:

black_knight(Attack) when is_function(Attack, 0) –>

    try Attack() of

        _ -> "None shall pass."

    catch

        throw:slice   -> "It is but a scratch.";

        error:cut_arm -> "I’ve had worse.";

        exit: cut_leg -> "Come on you pansy!";

        _:_             -> "Just a flesh wound."

    after

        io:format("Attack finished…~n", [])

    end.


 

Whenever you’re ready, here are 4 ways I can help you:

  1. If you want a one-stop shop to help you quickly level up your serverless skills, you should check out my Production-Ready Serverless workshop. Over 20 AWS Heroes & Community Builders have passed through this workshop, plus 1000+ students from the likes of AWS, LEGO, Booking, HBO and Siemens.
  2. If you want to learn how to test serverless applications without all the pain and hassle, you should check out my latest course, Testing Serverless Architectures.
  3. If you’re a manager or founder and want to help your team move faster and build better software, then check out my consulting services.
  4. If you just want to hang out, talk serverless, or ask for help, then you should join my FREE Community.

 


2 thoughts on “What does this F# code look like in Erlang – Part 3 of N”

  1. Pingback: What does this F# code look like in Erlang – Part 2 of N | theburningmonk.com

  2. Pingback: What does this F# code look like in Erlang – Part 1 of N | theburningmonk.com

Leave a Comment

Your email address will not be published. Required fields are marked *