Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0143: Conditional Conformances

What is your evaluation of the proposal? +1 with concern about the least specialized implementation winning. I think that this could be tricky to explain or build an intuition around. Is the problem being addressed significant enough to warrant a change to Swift? Yes Does this proposal fit

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0143: Conditional Conformances

Comments on: The review of “Conditional Conformances” begins now and runs through October 7. The proposal is available here: https://github.com/apple/swift-evolution/blob/master/ proposals/0143-conditional-conformances.md - What is your evaluation of the proposal? Great - Is the problem

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0143: Conditional Conformances

> What is your evaluation of the proposal? Huge +1. Conditional conformances are at the very top of the list of frustrating limitations in Swift. Lifting that limitation can’t happen soon enough for me. I have some concern that the restriction on overlapping conformances could continue to

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0143: Conditional Conformances

> On Sep 29, 2016, at 6:46 PM, Brent Royal-Gordon via swift-evolution > wrote: > >> • What is your evaluation of the proposal? > > This is a massively important and must-have feature. > > However, I'm dismayed by the size and complexity of the "detailed

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0143: Conditional Conformances

> • What is your evaluation of the proposal? This is a massively important and must-have feature. However, I'm dismayed by the size and complexity of the "detailed design" section. There are a *lot* of little nooks and crannies to this proposal. How certain are we that we've identified