swift-api-design-guidelines

Swift API naming uses grammatical phrasing and prepositional argument labels to create fluent, unambiguous call sites. It enforces consistent naming conventions across methods to ensure they read naturally at the point of use.

Use mutating vs nonmutating naming in Swift by applying -ed/-ing forms or form-prefix patterns for clarity. This distinction clarifies whether a method modifies state in place or returns a new value.

Standardize Swift protocol naming and documentation comments by applying consistent casing, grammatical rules, and default arguments. This improves API consistency and makes interfaces easier to understand.

Prepositional argument labels in Swift API design guide fluent call sites by clarifying the relationship between parameters. They enforce grammatical phrasing to make method signatures read naturally.

Swift API design suffers from ambiguous argument labels when naming is inconsistent or grammatical phrasing is ignored. Applying rules for prepositional labels and default arguments resolves call-site readability issues.

Use make-prefixed factories and form prefixes in Swift to align with API design guidelines for clear naming. They distinguish factory methods and type-conversion methods from mutating pairs, improving readability.