early_returns

Macros to make early returns and loop breaks/continues easier to work with in Rust

Motivation

When working with optional values or result values, it can often be beneficial to code readability to use early returns to "bail out" if an option is not engaged (e.g. if it is None). However, if the function's return type is the unit type, the ? operator cannot be used, which can lead to overly-verbose constructs like nested if-let blocks.

Additionally, the ? operator cannot be used in loops, where it might be useful to break or continue if an option is None or a result is Err.

What this crate provides

This crate hopes to make working with such types simpler by providing macros that will get the underlying type or return from the function or break from/continue in loops immediately.

The macros for Option are: * some_or_return * Will "extract" a Some value if available or return from the current function. * some_or_break * Will "extract" a Some value if available or break from either the current loop (if no loop lifetime is specified) or the specified loop (if a loop lifetime is specified). * some_or_continue * Will "extract" a Some value if available or continue either the current loop (if no loop lifetime is specified) or the specified loop (if a loop lifetime is specified).

The macros for Result are: * ok_or_return * Will "extract" an Ok value if available or return from the current function. * ok_or_break * Will "extract" an Ok value if available or break from either the current loop (if no loop lifetime is specified) or the specified loop (if a loop lifetime is specified). * ok_or_continue * Will "extract" an Ok value if available or continue either the current loop (if no loop lifetime is specified) or the specified loop (if a loop lifetime is specified).

Examples

Early return from a function

The motivating example is something like this: rust fn print_if_all_available_nested(a: Option<i32>, b: Option<i32>, c: Result<i32, ()>) { if let Some(a) = a { if let Some(b) = b { if let Ok(c) = c { println!("{a} + {b} + {c} = {}", a + b + c); } } } } As the nesting gets deeper or more complicated, it can be difficult for readers to follow. By returning early, readers can more easily follow the logic of the function, but there's no simple way to do this. For example, the following works and is easy to read, but includes a lot of boiler plate. ```rust fn printifallavailableverbose(a: Option, b: Option, c: Result

let b = if let Some(b) = b {
    b
} else {
    return;
};

let c = if let Ok(c) = c {
    c
} else {
    return;
};

println!("{a} + {b} + {c} = {}", a + b + c);

} ```

This crate provides macros to reduce this boilerplate, so the above can be replaced with: ```rust fn printifallavailablemacro(a: Option, b: Option, c: Resultorreturn!(a); let b = someorreturn!(b); let c = okorreturn!(c);

println!("{a} + {b} + {c} = {}", a + b + c);

} ```

Continuing in a loop

Similarly, there are macros that can be used to break or continue in loops. For example, this: rust fn do_something_with_vec_of_optionals(values: &Vec<Option<i32>>) { for value in &values { let value = if let Some(value) = value { value } else { continue; }; something(value); } }

can be reduced to this:

rust fn do_something_with_vec_of_optionals(values: &Vec<Option<i32>>) { for value in values { let value = some_or_continue!(value); something(value); } }