> Like, in Ruby, where everything truly is an expression, importing a file and then evaluating it has side effects. In the context of ML, I think it's a more u

> Like, in Ruby, where everything truly is an expression, importing a file and then evaluating it has side effects. In the context of ML, I think it's a more useful baseline. So declarations are still declarations, but e.g. ; is just a sequential evaluation operator. > let being a statement is nice because it means it can only happen at the "top level" of a block, and not say, inside a loop condition. I would argue that it's actually a downside - it means that a loop condition cannot have common subexpressions (that nevertheless need to be evaluated on every iteration) factored out.