Comment Comment by troupo > It separates "names as public-facing API design decisions" from "names as developer conveniences for expressing intent and clarifying their code"How often is this an issue?> And unlike Smalltalk, in Swift at least, externally unnamed but internally named is easy (just make the external name _).So, visual clutter for very little gain. IMO parent troupo 3 years ago
How often is this an issue?
> And unlike Smalltalk, in Swift at least, externally unnamed but internally named is easy (just make the external name _).
So, visual clutter for very little gain. IMO