There's an interesting thing with the semicolon. I've heard people advocating thinking of the semicolon as a binary operator: (;) : unit -> unit -> unit Of co

There's an interesting thing with the semicolon. I've heard people advocating thinking of the semicolon as a binary operator: (;) : unit -> unit -> unit Of course, the reality is more complicated than this, because it can be used at the end of an expression, where it behaves like a postfix operator of type 'a -> 'a. Let's take your example: match left with | Some left -> match right with | Some right -> Some (left, right) | None -> None | None -> None you can actually do match left with | Some left -> match right with | Some right -> Some (left, right) | None -> None ; ; (* <-- two separate semicolons *) | None -> None This doesn't just work for imperative stuff, like the operator theory of the semicolon, it will work with this example. My understanding is that this is due to the fact that optional semicolons are allowed at the end of statements and close the current expression. So we're closing the first expression (None) and then closing the second expression (the inner match). The double semicolon is something else altogether. Though it is worth noting that this example is straying from idiomatic OCaml and we can avoid this altogether with better matching: match (left, right) with | (Some left, Some right) -> Some (left, right) | _ -> None Both the native optimizing compiler and BuckleScript are able to do what you would expect with this: the matched tuple is optimized away. Your second unfixed example actually causes a syntax error. There is an if expression in OCaml and an if statement. This is particularly unfortunate, because the let cache_file = function | file when file_exists file -> printf "downloading file\n"; download file | _ -> printf "file already exists\n" first semicolon within an if expression turns the whole thing into an if statement, and an if statement can have no else clause. The else clause is then without an if statement, because we've triggered the imperative if statement. This is a syntax error. were we to define an operator let (>>>) a b = a; b then we could replace that semicolon with an >>> and things behave as expected. But it's really that if can be both a statement and an expression. For this reason I prefer using matches in general. let cache_file = function | file when not (file_exists file) -> printf "downloading file\n"; download file | _ -> printf "file already exists\n"