<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Good question. I suppose the dot syntax is a special syntax, so .{} would also be a special syntax.<br><br>Pierre</div><div><br>Le 14 déc. 2015 à 10:02, Jacob Bandes-Storch <<a href="mailto:jtbandes@gmail.com">jtbandes@gmail.com</a>> a écrit :<br><br></div><blockquote type="cite"><div><div dir="ltr">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">http://ruby-doc.org/core-2.2.0/BasicObject.html#method-i-instance_eval</a>>)?<div class="gmail_extra"><br clear="all"><div><div><div dir="ltr"><div>Jacob<br></div></div></div></div>
<br><div class="gmail_quote">On Mon, Dec 14, 2015 at 12:03 AM, Pierre Monod-Broca via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><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>
<br>
Pierre<br>
<div><div><br>
> Le 11 déc. 2015 à 18:05, Kenny Leung via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> a écrit :<br>
><br>
> 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>
><br>
> This<br>
><br>
> myObject {<br>
> this = that<br>
> here = there<br>
> }<br>
><br>
> could unambiguously indicate that you want method cascading.<br>
><br>
> Or even<br>
><br>
> myObject.{<br>
> this = that<br>
> here = there<br>
> }<br>
><br>
> which has a relationship to the current method invocation syntax.<br>
><br>
> -Kenny<br>
><br>
><br>
>> On Dec 9, 2015, at 9:47 AM, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
>><br>
>> Here you go: <a href="https://bugs.swift.org/browse/SR-160" rel="noreferrer" target="_blank">https://bugs.swift.org/browse/SR-160</a><br>
>><br>
>> Let me also point you to this: <a href="https://gist.github.com/erica/6794d48d917e2084d6ed" rel="noreferrer" target="_blank">https://gist.github.com/erica/6794d48d917e2084d6ed</a> because<br>
>><br>
>> * It is pretty<br>
>> * I put a lot of effort into it, following the "social" request in the current process document, etc<br>
>> * I want to publicly shower props on Sean Heber, who showed great patience, insight, and kindness helping out on this<br>
>><br>
>> I'd appreciate any advice you could share on determining which tool to use when you have a Swift enhancement idea<br>
>><br>
>> -- E<br>
>><br>
>><br>
>>> On Dec 8, 2015, at 10:16 PM, Chris Lattner <<a href="mailto:clattner@apple.com" target="_blank">clattner@apple.com</a>> wrote:<br>
>>><br>
>>><br>
>>>> On Dec 7, 2015, at 4:46 PM, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
>>>><br>
>>>> 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>
>>><br>
>>> Personally, I’d rather use <a href="http://bugs.swift.org" rel="noreferrer" target="_blank">bugs.swift.org</a> for feature requests like this. It is lighter weight, allows commenting, etc.<br>
>>><br>
>>> -Chris<br>
>>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> swift-evolution mailing list<br>
>> <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
>> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
><br>
> _______________________________________________<br>
> swift-evolution mailing list<br>
> <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</div></div></blockquote></div><br></div></div>
</div></blockquote></body></html>