[Pre-RFC] pseudo-closures

[scottmcm]

@Nokel81

Example 1: returning from parent function in a “non-moveable” closure construct

Probably not, see

pre-RFC: Allow return, continue, and break to affect the captured environment

The general idea is that inside a closure, return; would return from the defining function instead of the closure. fn main() { // `return` would be a divergent expression and return from `main` let id: i32 = "321".parse().or_else(|| return); } This would allow Rust to satisfy the Tennent’s Correspondence Principle. In short, Tennent’s Correspondence Principle says: For a given expression expr, || expr should be equivalent. You could wrap arbitrary parts function body (even the whole f…

@Nokel81

Example 2: using continue and break as “closures”

Same problem. Use try_fold instead of fold, and similar, instead.