[swift-evolution] RFC: didset and willset

Leonardo Pessoa me at lmpessoa.com
Wed May 18 16:05:23 CDT 2016

Matthew's right. The first thing here is to define a consistent rule
which takes no exceptions and then apply this rule to every existing
or new keyword and attribute.

On 18 May 2016 at 18:02, Matthew Johnson <matthew at anandabits.com> wrote:
>> On May 18, 2016, at 3:55 PM, Brent Royal-Gordon via swift-evolution <swift-evolution at swift.org> wrote:
>>> I may be wrong but I don't remember any other case of a keyword in
>>> Swift composed of two or more words, so I believe these should be
>>> exceptions.
>> `typealias` and `associatedtype` are the main examples; there were huge catfights on swift-evolution about whether the latter should be `associatedtype`, `associatedType`, or `associated_type`. There are also a number of attributes like `@noescape` and `@discardableResult`, which aren't 100% consistent.
> Yeah, some of these changes which may feel like low hanging fruit to some turn out to take a lot of energy.
> If we’re going to pursue more of these kinds of changes, I would prefer a comprehensive proposal that evaluates everything, establishes well defined conventions, and then applies the changes holistically.
>> --
>> Brent Royal-Gordon
>> Architechies
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org
>> https://lists.swift.org/mailman/listinfo/swift-evolution

More information about the swift-evolution mailing list