-1
> I'm not sure this intermediate churn is really worth it.
That has been my opinion in the original thread, and I haven't read anything
that changed my mind:
Better live with a tiny inconsistency now than deal with three different forms
of didSet/willSet in the future.
> * What is your evaluation of the proposal?
If we are absolutely, 100% sure that we are going to use lowercase naming for
other accessors, including user-defined ones for property behaviors, then I see
no reason not to do this now. If we are less than, say, 95% sure, I don't think
we sho
I totally agree with the arguments brought forth by John and Joe.
Therefore -1 to the proposal
-Thorsten
Am 24.05.2016 um 20:39 schrieb John McCall via swift-evolution
:
>> On May 24, 2016, at 11:21 AM, Joe Groff via swift-evolution
>> wrote:
>> didSet and willSet are already contextual rat
On Tue, May 24, 2016, at 11:07 AM, Chris Lattner wrote:
> * What is your evaluation of the proposal?
-1. The only real rationale here is "other keywords that are compound words are
all lowercase instead of camelCase" (except for dynamicType). But that's not a
very compelling argument. More
> On May 24, 2016, at 2:07 PM, Chris Lattner wrote:
>
> Hello Swift community,
>
> The review of "SE-0098: Lowercase didSet and willSet for more consistent
> keyword casing" begins now and runs through May 30. The proposal is available
> here:
>
>
> https://github.com/apple/swift-evol
> On May 24, 2016, at 11:21 AM, Joe Groff via swift-evolution
> wrote:
> didSet and willSet are already contextual rather than formal keywords, and
> there's a conceivable future where didSet and willSet are no longer keywords
> at all if we run with the "property behaviors" feature again in th
Sent from my iPad
> On May 24, 2016, at 1:21 PM, Joe Groff via swift-evolution
> wrote:
>
> didSet and willSet are already contextual rather than formal keywords, and
> there's a conceivable future where didSet and willSet are no longer keywords
> at all if we run with the "property behavio
+1.
If Swift is going to state that keywords need to be lowercased, conjoined
words, then there should be no exceptions to that rule without some fairly
significant gain.
It’s also a fairly low-impact change for any fixit to be run.
-David
> On May 24, 2016, at 11:21 AM, Joe Groff via swift
didSet and willSet are already contextual rather than formal keywords, and
there's a conceivable future where didSet and willSet are no longer keywords at
all if we run with the "property behaviors" feature again in the future. If we
think that's likely, I'm not sure this intermediate churn is r
