In the article they discuss that Rust closures are just sugar for structs that work exactly as you describe. As with any other syntactic sugar, it's easy to re

In the article they discuss that Rust closures are just sugar for structs that work exactly as you describe. As with any other syntactic sugar, it's easy to reason about the behavior once you know what the syntax desugars into. One classic example I see with beginning programmers all the time is the order of the parts of a for loop. e.g. for(initialization statement; bounds check expression; increment statement) { ... } is just syntactic sugar for: { initialization statement; while (bounds check expression) { ... increment statement; } } But once you understand what a for-loop desugars into, it's trivial to use and reason about. Closures aren't much different. In Rust, if anything, they're less magic, because you have to be explicit about the lifetime of the closure relative to the references it's borrowing.