Why not simply FnOnce, FnFew?

All in all, think of the Fn… traits as: FnOnce() is CallableThroughOwnedAccess: trait CallableThroughOwnedAccess { fn call(self); } FnMut() is CallableThroughUniqueAccess: trait CallableThroughUniqueAccess { fn call(&mut self); } Fn() is CallableThroughSharedAccess: trait CallableThrough…

Rationale behind Fn, FnMut and FnOnce design

help

H2CO3 September 3, 2021, 11:40am 11

In Rust, soundness is never just a convention.

12 Likes

TWiR quote of the week

Topic		Replies	Views
Is there ever a use for non-thread safe `Fn` bounds? help	10	353	March 3, 2024
Rust Closure: fn to Fn*	4	1099	January 12, 2023
Expected a closure that implements the `FnMut` trait, but this closure only implements `FnOnce` help	10	7305	March 3, 2022
Async closure thoughts from Michael Goulet (compiler-errors) and thanks for his contributions!	2	214	September 30, 2024
Fn traits, call and call_once mechanism (ignoring call_mut for simplicity) help	5	70	February 13, 2025

Rationale behind Fn, FnMut and FnOnce design

Related topics