[swift-evolution] Argument of '#selector' cannot refer to a property?

[David Hart]

I’ll write it up.

> On 22 Feb 2016, at 23:25, Douglas Gregor <dgregor at apple.com> wrote:
> 
> 
>> On Feb 22, 2016, at 2:24 PM, Joe Groff <jgroff at apple.com <mailto:jgroff at apple.com>> wrote:
>> 
>> 
>>> On Feb 22, 2016, at 2:18 PM, Douglas Gregor <dgregor at apple.com <mailto:dgregor at apple.com>> wrote:
>>> 
>>>> 
>>>> On Feb 22, 2016, at 2:14 PM, Joe Groff <jgroff at apple.com <mailto:jgroff at apple.com>> wrote:
>>>> 
>>>> 
>>>>> On Feb 22, 2016, at 2:09 PM, Douglas Gregor <dgregor at apple.com <mailto:dgregor at apple.com>> wrote:
>>>>> 
>>>>>> 
>>>>>> On Feb 22, 2016, at 1:50 PM, David Hart <david at hartbit.com <mailto:david at hartbit.com>> wrote:
>>>>>> 
>>>>>> Is a design for lenses imaginable for Swift 3.0 or is that completely out of scope?
>>>>> 
>>>>> I was going to say “imaginable”, but property behaviors is taking up far more design and engineering time than I’d hoped, and at this point I’m expecting lenses to fall off the Swift 3 schedule. JoeG might have more insight here.
>>>> 
>>>> Yeah, I don't think lenses will fit into Swift 3 at this point. Since we've taken a special #-form for selector references, I wouldn't feel too bad about inventing some ad-hoc syntax for naming the get and set selectors for an @objc property.
>>> 
>>> Something like #selector(getter: <PROPERTY>) and #selector(setter: <PROPERTY>) would fit easily enough.
>> 
>> SGTM.
> 
> Someone want to write this up as a follow-on proposal?
> 
> 	- Doug
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160223/b1f41f19/attachment.html>