<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Joe Groff pointed out that a leading . was syntactically ambiguous. From 7 December 2015:</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><span style="font-family: Palatino-Roman;" class="">Note that using leading '.' is syntactically ambiguous. The above already parses as `.thing = 42.otherThing("meaning of life")` (or would, if we didn't already ban statements from starting with '.' for exactly this reason).</span><br style="font-family: Palatino-Roman;" class=""><br style="font-family: Palatino-Roman;" class=""><span style="font-family: Palatino-Roman;" class="">-Joe</span></blockquote></div><div class=""><br class=""></div><div class="">-- E</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 14, 2015, at 2:02 AM, Jacob Bandes-Storch via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Would .{} be a special syntax in the grammar, or an instance of a custom operator taking advantage of some more generic self-rebinding? Would you be able to write a custom function taking such a block and applying it later (à la instance_eval <<a href="http://ruby-doc.org/core-2.2.0/BasicObject.html#method-i-instance_eval" class="">http://ruby-doc.org/core-2.2.0/BasicObject.html#method-i-instance_eval</a>>)?<div class="gmail_extra"><br clear="all" class=""><div class=""><div class=""><div dir="ltr" class=""><div class="">Jacob<br class=""></div></div></div></div>
<br class=""><div class="gmail_quote">On Mon, Dec 14, 2015 at 12:03 AM, Pierre Monod-Broca via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">+1, the .{} syntax is nice<br class="">
<br class="">
Pierre<br class="">
<div class=""><div class=""><br class="">
> Le 11 déc. 2015 à 18:05, Kenny Leung via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>> a écrit :<br class="">
><br class="">
> I’m all for this, but couldn’t it be done without the “with”? It doesn’t seem to make the code read any easier.<br class="">
><br class="">
> This<br class="">
><br class="">
> myObject {<br class="">
> this = that<br class="">
> here = there<br class="">
> }<br class="">
><br class="">
> could unambiguously indicate that you want method cascading.<br class="">
><br class="">
> Or even<br class="">
><br class="">
> myObject.{<br class="">
> this = that<br class="">
> here = there<br class="">
> }<br class="">
><br class="">
> which has a relationship to the current method invocation syntax.<br class="">
><br class="">
> -Kenny<br class="">
><br class="">
><br class="">
>> On Dec 9, 2015, at 9:47 AM, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>> wrote:<br class="">
>><br class="">
>> Here you go: <a href="https://bugs.swift.org/browse/SR-160" rel="noreferrer" target="_blank" class="">https://bugs.swift.org/browse/SR-160</a><br class="">
>><br class="">
>> Let me also point you to this: <a href="https://gist.github.com/erica/6794d48d917e2084d6ed" rel="noreferrer" target="_blank" class="">https://gist.github.com/erica/6794d48d917e2084d6ed</a> because<br class="">
>><br class="">
>> * It is pretty<br class="">
>> * I put a lot of effort into it, following the "social" request in the current process document, etc<br class="">
>> * I want to publicly shower props on Sean Heber, who showed great patience, insight, and kindness helping out on this<br class="">
>><br class="">
>> I'd appreciate any advice you could share on determining which tool to use when you have a Swift enhancement idea<br class="">
>><br class="">
>> -- E<br class="">
>><br class="">
>><br class="">
>>> On Dec 8, 2015, at 10:16 PM, Chris Lattner <<a href="mailto:clattner@apple.com" target="_blank" class="">clattner@apple.com</a>> wrote:<br class="">
>>><br class="">
>>><br class="">
>>>> On Dec 7, 2015, at 4:46 PM, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>> wrote:<br class="">
>>>><br class="">
>>>> Noted. Since an updated proposal is all but ready, could we please have a Swift 4 proposal daycare folder to stick it in, so it doesn't get lost or forgotten?<br class="">
>>><br class="">
>>> Personally, I’d rather use <a href="http://bugs.swift.org/" rel="noreferrer" target="_blank" class="">bugs.swift.org</a> for feature requests like this. It is lighter weight, allows commenting, etc.<br class="">
>>><br class="">
>>> -Chris<br class="">
>>><br class="">
>><br class="">
>><br class="">
>> _______________________________________________<br class="">
>> swift-evolution mailing list<br class="">
>> <a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
>> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
><br class="">
> _______________________________________________<br class="">
> swift-evolution mailing list<br class="">
> <a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
<br class="">
_______________________________________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
</div></div></blockquote></div><br class=""></div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=r5jpKsi6nat7oa43lpCLi5GRGm2utDkbDscuFklXZ2dKlJnH40AMjTVXU6x6VgR5oTEXjwyQ66nMrSySM0UOWRIu4OFCZA0kE9Wq-2BejPP6in1WNgMnSuyZaXszUMzhlFh-2FaIimQKvOKu9df0zS6WtnLudHm-2F8hhnKvVDsC-2FMycbh4SJSIkE7vy792VHbSRizKEhUI0G3CmRTlHuR9IiUdyKM1iJBj-2FgXWGm9n2YyTLo-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>