[swift-evolution] Proposal: Expose getter/setters in the same way as regular methods
matthew at anandabits.com
Sun Dec 13 18:58:36 CST 2015
> I find that (KVO) one of Objective-C's most annoying features. It makes it really difficult to reason about code when things can happen unexpectedly left and right. It's the same issue with aspect-oriented programming.
> I prefer explicit integration points like closures, delegates and alike.
+1. I especially dislike system APIs that offer no alternatives to KVO when communicating with clients. I hope we can at least avoid that mistake in Swift-native API designs.
> Being able to refer to getters and setters is a good idea and aligns with being able to refer to initializers and methods.
> I would also add subscripts to the list if possible.
+1 to this as well.
More information about the swift-evolution