Re: [swift-evolution] [Review] SE-0153: Compensate for the inconsistency of @NSCopying's behaviour

2017-02-18 Thread Rod Brown via swift-evolution
> What is your evaluation of the proposal? It’s clearly a concern and one that should be addressed. A lot of people have bought up the didSet {} property observers are not called when things are set here, either. This is true, but unlike property observers, these are attributes, and I don’t kno

Re: [swift-evolution] [Review] SE-0153: Compensate for the inconsistency of @NSCopying's behaviour

2017-02-18 Thread Torin Kwok via swift-evolution
Hello Swift community: Thank you for your reviews for my proposal. As you may have seen, this proposal contains two solutions originally: Compiler magic Compile-time checking However even though Solution: Compiler magic is viable, according to some of feedback from several reviewers, a develope

Re: [swift-evolution] [Review] SE-0153: Compensate for the inconsistency of @NSCopying's behaviour

2017-02-17 Thread David Waite via swift-evolution
> > Proposal link: > > https://github.com/apple/swift-evolution/blob/master/proposals/0153-compensate-for-the-inconsistency-of-nscopyings-behaviour.md > > > > What

Re: [swift-evolution] [Review] SE-0153: Compensate for the inconsistency of @NSCopying's behaviour

2017-02-17 Thread David Hart via swift-evolution
>> What is your evaluation of the proposal? For the same reasons as Xiaodi, this proposal could be potentially misleading if it introduces custom compiler magic, warning or errors that was not replicated for future property behaviours. But at the same time, it's very easy for even a seasoned d

Re: [swift-evolution] [Review] SE-0153: Compensate for the inconsistency of @NSCopying's behaviour

2017-02-17 Thread Xiaodi Wu via swift-evolution
> > >- What is your evaluation of the proposal? > > This document seems to propose two contradictory alternative solutions; I assume the goal is that the core team will choose one of two. I'm not sure that either is an improvement over the status quo, for reasons I outline below. > >- Is

[swift-evolution] [Review] SE-0153: Compensate for the inconsistency of @NSCopying's behaviour

2017-02-17 Thread Douglas Gregor via swift-evolution
Hello Swift community, The review of SE-0153 "Compensate for the inconsistency of @NSCopying's behaviour" begins now and runs through February 22, 2017. The proposal is available here: https://github.com/apple/swift-evolution/blob/master/proposals/0153-compensate-for-the-inconsistency-of-nscopy