If that's the case, force unwrapping can be done with a different symbol. Personally I like '!' for force unwrapping.
On Wed, Feb 15, 2017 at 11:45 PM, Jose Cheyo Jimenez <[email protected]> wrote: > https://lists.swift.org/pipermail/swift-evolution/ > 2015-December/000032.html > > Swift tries to be part of the C family of languages so keeping all the > familiar symbols is on purpose. See the ?: operator. > > > On Feb 15, 2017, at 10:01 AM, Sadiq <[email protected]> wrote: > > I tried to find it there. I did not find it. You mean here > > https://github.com/apple/swift-evolution/blob/master/commonly_proposed.md > > right? > > On Wed, Feb 15, 2017 at 11:27 PM, Jose Cheyo Jimenez <[email protected]> > wrote: > >> Hi Mohammad, >> >> This has been proposed before. Please see the commonly rejected section >> in the GitHub repo for Swift Evolution. >> >> Thanks! >> >> >> On Feb 15, 2017, at 6:02 AM, Sadiq via swift-evolution < >> [email protected]> wrote: >> >> Hello, >> >> I would like to suggest to change Logical NOT Operator from ! to >> something else. >> It will increase the readability of the code and will avoid any confusion >> with the symbol used for force unwrapping of optional values. >> It would be easier for new programmers to learn Swift as the first >> language. >> I don't understand the rational behind using the same operator for two >> different purposes. >> >> Thanks and Regards, >> Mohammad Sadiq >> >> _______________________________________________ >> 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
