Option monads have the same semantics as C# null described in the article; they don't apply the function if the value isn't present, you get another non-present

Option monads have the same semantics as C# null described in the article; they don't apply the function if the value isn't present, you get another non-present value back out. Result<,> has the same semantics as checked exceptions, BTW. The conversion between the two representations of code is mechanical. Checked exceptions are a poor idea the more dynamically bound your language is, and are generally anti-abstraction in any case (failure modes are implementation specific, i.e. non-conformant with an information hiding interface). An error result is only useful if you can make a decision based on the specific value; that's not the case for almost all sources of error in most user (i.e. non-system) programs, where complete coverage of error cases with specific handlers is outside their design parameters, and termination (of program or request or whatever) is preferable.