Description
openedon Apr 22, 2019
We've been moving away from the "static method" terminology, so IMO we should be more uniform with all associated items, and treat the general case of "methods that may or may not have self
" as simply "associated functions".
"Method" terminology would then remain primarily for "method call", i.e. dot syntax for asymmetrically providing the self
argument.
Because AssociatedFn
is a bit long, I'd find it fitting if we shortened Associated
, across rustc, to Assoc
, so we end up with AssocFn
(which only one letter longer than Method
).
Also, when Method
appears in the context of associated items already (e.g. {Trait,Impl}ItemKind
), it can be just Fn
.
cc @rust-lang/compiler (and in particular, I'm curious what @nikomatsakis thinks the decision process for "cosmetic" changes like these should be)