Ha! You clicked send 4 minutes before I did :-) > On Jun 29, 2016, at 7:48 AM, Taras Zakharko via swift-evolution > <[email protected]> wrote: > > Just a quick clarification: I was under impression that the utility of > Boolean was that one could extend any type to behave as a boolean type and > thus be used in control flow constructions etc. Not something that has to do > often, but nice to have nevertheless. I would be sad if this functionality > were to go. At the same time, I understand the rationale behind this > proposal. Maybe we could introduce something like CustomBoolConvertible > instead (if not yet suggested)? > > Best, > > Taras > > >> On 29 Jun 2016, at 08:44, Douglas Gregor via swift-evolution >> <[email protected] <mailto:[email protected]>> wrote: >> >> Hello Swift community, >> >> The review of SE-0109 "Remove the Boolean protocol" begins now and runs >> through July 4, 2016. The proposal is available here: >> >> https://github.com/apple/swift-evolution/blob/master/proposals/0109-remove-boolean.md >> >> <https://github.com/apple/swift-evolution/blob/master/proposals/0109-remove-boolean.md> >> Reviews are an important part of the Swift evolution process. All reviews >> should be sent to the swift-evolution mailing list at >> >> https://lists.swift.org/mailman/listinfo/swift-evolution >> <https://lists.swift.org/mailman/listinfo/swift-evolution> >> or, if you would like to keep your feedback private, directly to the review >> manager. When replying, please try to keep the proposal link at the top of >> the message: >> >> Proposal link: >> >> https://github.com/apple/swift-evolution/blob/master/proposals/0109-remove-boolean.md >> >> <https://github.com/apple/swift-evolution/blob/master/proposals/0109-remove-boolean.md> >> Reply text >> >> Other replies >> <https://github.com/apple/swift-evolution#what-goes-into-a-review-1>What >> goes into a review? >> >> The goal of the review process is to improve the proposal under review >> through constructive criticism and, eventually, determine the direction of >> Swift. When writing your review, here are some questions you might want to >> answer in your review: >> >> What is your evaluation of the proposal? >> Is the problem being addressed significant enough to warrant a change to >> Swift? >> Does this proposal fit well with the feel and direction of Swift? >> If you have used other languages or libraries with a similar feature, how do >> you feel that this proposal compares to those? >> How much effort did you put into your review? A glance, a quick reading, or >> an in-depth study? >> More information about the Swift evolution process is available at >> >> https://github.com/apple/swift-evolution/blob/master/process.md >> <https://github.com/apple/swift-evolution/blob/master/process.md> >> Thank you, >> >> -Doug >> >> Review Manager >> >> _______________________________________________ >> swift-evolution mailing list >> [email protected] <mailto:[email protected]> >> https://lists.swift.org/mailman/listinfo/swift-evolution > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
