impl Trait
s as function arguments are desugared to an anonymous generic parameter. See the RFC, which says:
Expand impl Trait
to allow use in arguments, where it behaves like an anonymous generic parameter.
There's also an example in the RFC:
// These two are equivalent
fn map<U>(self, f: impl FnOnce(T) -> U) -> Option<U>
fn map<U, F>(self, f: F) -> Option<U> where F: FnOnce(T) -> U
However, one difference is that impl Trait
arguments cannot have their types explicitly specified:
fn foo<T: Trait>(t: T)
fn bar(t: impl Trait)
foo::<u32>(0) // this is allowed
bar::<u32>(0) // this is not
The Motivation for expanding to argument position section explains why additional syntax was added for an existing feature. In short, it's for having similar syntax as impl
traits in function return position, which improves learnability, and to improve ergonomics.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…