Comment by rtpg
6 hours ago
I remember really bumping up against this learning OCaml in college after having experienced oodles of imperative programming.
I understand the sort of philosophy and ergonomics of not having an early return, but it really does hurt certain kinds of code that otherwise would be more readable
> ergonomics of not having an early return
I wonder who came up with this idea first. I find obvious early returns incredibly ergonomic.
Wikipedia says that "guard clause" was a term invented by Kent Beck, but that the actual practice was used since at least the early 60s
No, I meant the idea that guard clauses are antipatterns and your subroutine should have a single implicit return.
1 reply →