[swift-evolution] Proposal: Universal dynamic dispatch for method calls
gwendal.roue at gmail.com
Wed Dec 9 16:14:11 CST 2015
> Le 9 déc. 2015 à 23:07, Brent Royal-Gordon <brent at architechies.com> a écrit :
>> Yet, to me, `(self as P).f()`, targeted to the struct writer who has read the doc because he has a feature to write, looks odd, but less dangerous than a public _f function that is available to the struct user who *has not read the manual*. People don’t read the doc unless they have a strong need for it.
> You don’t have to read the manual to know that you keep your mitts off something with an `_` prefix unless you know what you’re doing.
Yes, and this is really the reason why a `_` prefix is bad for a use case that should be ranked Easy in the Obvious / Easy / Possible scale (https://signalvnoise.com/posts/3047-the-obvious-the-easy-and-the-possible)
More information about the swift-evolution