Isn't this already done, at least for enum cases? I'm pretty sure I've seen discussion of this before, and I thought it might've gotten implemented. On Fri, Jun 17, 2016 at 1:45 PM E. Maloney via swift-evolution < [email protected]> wrote:
> While upgrading to Swift 3, I noticed that I had a few enums with cases > named .Default that, after being converted to lowercase, now need to be > rendered using the ugly .`default` notation. > > I also noticed something similar while reading the docs for > NotificationCenter (the NSNotificationCenter replacement, that is, not the > NotificationCenter that governs the notification center UI); “default” > can’t be used as a function name without escaping, so the declaration is: > > class func `default`() > > It seems to me that in the case of function names and enum cases, the > parser should be able to unambiguously distinguish between the Swift > keyword “default” and a user-defined name “default”, since IIRC the keyword > “default” can only be used in parameter lists for generated headers and as > the last item in a switch statement. > > (Perhaps this is also another argument in favor of using “case _:” in > place of “default:” in a switch statement.) > > What do you think? Is there any reason this *wouldn’t* be feasible? > _______________________________________________ > 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
