Re:A lambda is not necessarily a closure
by dbaupp on Tuesday February 09, 2016 @06:14AM
(#11064564)
Only `proc` closures were boxed, `|...| -> ...` closures were pointers into the stack. However, it is true that all closures were type erased, and were hence equivalent to certain trait object types (`Box<FnOnce(...) -> ...>` for `proc`, and `&mut FnMut(...) -> ...` for the pipes).
Also, functions could coerce to either of the closure types, and hence be passed straight to functions expecting them.
Re:A lambda is not necessarily a closure
by Manishearth on Tuesday February 09, 2016 @06:35AM
(#11064625)
> Also, functions could coerce to either of the closure types
Huh, I recall this not working. Perhaps I made a mistake then.
> closures were pointers into the stack
Ah, the type erasure was through &mut. TIL; I always thought it was Box only.
Post "unboxed closures", closures are now stored on the stack (thus they usually optimize away; for example if you use an iterator with a bunch of adapters like filter/map it will optimize down to a for loop). Each closure has a unique anonymous type (you can box them if you want them to have the same type), and all closures implement one or more of the Fn* traits, as do function pointers. So arguments can be generic over all callables, and you can pass in a closure or a function or your own custom callable.