[swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false

Adrian Zubarev adrian.zubarev at devandartist.com
Thu May 5 06:04:28 CDT 2016

-1 as well. Everything has already been said by the community. Swift should evolve on its own and don't care around old garbage. true and false is and was the best way to express a boolean.

Adrian Zubarev  

Am 5. Mai 2016 um 11:56:55, Jacopo Andrea Giola via swift-evolution (swift-evolution at swift.org(mailto:swift-evolution at swift.org)) schrieb:

> -1 for me as well.
> One of the most FAQ of other fellow developers coming from other languages are often confuse by the YES/NO boolean in Obj-C and always asks why I use those and not true/false (and don’t get me started on nil/Nil/NULL).
> I don’t want to find in the future discussion on StackOverflow with titles like “What are the differences between true/yes/on and false/no/off in Swift?” or “Is more correct to use yes or on in method x?”
> Jacopo
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160505/7a443f15/attachment.html>

More information about the swift-evolution mailing list