[swift-users] Coding style for internal/private variables

Erica Sadun erica at ericasadun.com
Wed Jun 1 11:52:15 CDT 2016

From what I've observed, preceding (rather than trailing) single underscores indicate private use. The standard library includes a fair number of "Apple Internal" (I guess now "Swift Team Internal") variables, methods, functions, etc that follow this practice. This practice is, as far as I can tell, uncoupled with access levels. A function named _foo(), while global and public, is still "hands off please".

All in all, other "Hungarian Style" conventions, that is modifying the name to indicate types and uses, are not used in Swift or among most Swift developers.

-- E

> On Jun 1, 2016, at 10:02 AM, Adrian Zubarev via swift-users <swift-users at swift.org> wrote:
> I’d like to talk about your personal coding styles in swift for its access control.
> Remember these variable names like __magic or _spell or even garbage_?
> Sure swift solves the synthesize problem but there might be old habits that let us write such code.
> Here are some examples:
> internal _name
> internal i_name
> private __name
> private p_name
> // not sure where `garbage_` would fit
> I’d love to see your responses and opinions what and why the style you choose suits you.
> -- 
> Adrian Zubarev
> Sent with Airmail
> _______________________________________________
> swift-users mailing list
> swift-users at swift.org <mailto:swift-users at swift.org>
> https://lists.swift.org/mailman/listinfo/swift-users <https://lists.swift.org/mailman/listinfo/swift-users>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-users/attachments/20160601/e2569c43/attachment.html>

More information about the swift-users mailing list