Re:Fantasy World OCaml (2013)
by rwmj on Sunday August 03, 2014 @08:47AM
(#8127779)
Because it would make a lot of code less nested and simpler to understand. The most common case is:
which would be replaced with:
The situation is particularly bad when you have to do a lot of small tests at the beginning of your function. Think permissions checks:
The alternative is to use exceptions, either hidden within the function (requiring a nested function), or demanding that the caller is careful about catching exceptions. Exceptions are an unsafe back door, when what's really needed is a return statement.
[ Parent
| on HN ]
Original code:
if some_error_condition then
None
else (
// everything else in the function is nested
)
Why not use a Maybe/Either monad like: x <- some_maybe_value
// everything else in the function isn't nested, and "x" is available (if some_maybe_value was Just)
Kind of like exceptions, but a bit more explicit.I don't understand your example. I don't want to run the "// everything else" bit if the error condition was true.
The error condition is represented by Nothing ("None" in OCaml?) and the rest of the code only runs if it was Just ("Some" in OCaml?).
A style I sometimes see is people not indenting the normal code path of the match. So your example above would be written:
match user with
| None -> printf "you need to specify a user\n"; None
| Some user_id when not (permitted user_id) ->
printf "this user is not permitted\n"; None
| Some user_id ->
// go ahead and return Some objectStay classy, downvoters. You know I've been a working OCaml programmer for the last 12 years, using the language most days, so I do know a bit about the pain points.