<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="">Hello Austin</div>I haven’t read that from Chris - Must have overlooked it due to the shear volume on swift-evolution.<div class=""><br class=""></div><div class="">Note that as you can see, I have apologised to Xiaodi for being </div><div class="">a bit too direct, such as perceived in your culture perhaps.</div><div class=""><br class=""></div><div class="">The Chinese characters should mean “respectful”” btw.</div><div class=""><br class=""></div><div class="">Apart from my perhaps fierce reaction, I am not aware of doing something wrong.</div><div class="">and I still find this topic very important. </div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class="gmail_extra"><div class="gmail_quote"><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;"><div class="" style="word-wrap: break-word;"><div class=""><div class="h5"><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><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;"><div class="" style="word-wrap: break-word;"><div class=""><div class=""><div class=""><div class="">4. read this on <a href="http://swift.org/" target="_blank" class="">Swift.org</a>: </div><div class=""><h3 id="m_-8905701175066207869m_4462182378981150637proposing-new-features" class="" style="box-sizing: border-box; margin: 0px 0px 0.5em; padding: 1em 0px 0px; font-weight: 400; line-height: 1; color: rgb(51, 51, 51);"><span class="" style="font-size: 12px;">"Proposing New Features"</span></h3><p class="" style="box-sizing: border-box; margin: 0px 0px 1.5em; padding: 0px; color: rgb(51, 51, 51);">"New features or directions for the Swift language can come from anyone with a good idea."</p><p class="" style="box-sizing: border-box; margin: 0px 0px 1.5em; padding: 0px; color: rgb(51, 51, 51);">"Open discussion and iteration over the ideas in a public forum is essential to reaching the best possible solutions."</p><div class="">also </div><div class=""><br class=""></div><div class=""><span class="" style="color: rgb(51, 51, 51); background-color: rgb(255, 255, 255);">"Everyone is welcome to propose, discuss, and review ideas to improve the Swift language and standard library on the </span><a href="https://swift.org/community/#swift-evolution" title="Swift evolution mailing list" target="_blank" class="" style="box-sizing: border-box; color: rgb(64, 120, 192); text-decoration: none;">swift-evolution mailing list</a><span class="" style="background-color: rgb(255, 255, 255);"><font color="#333333" class="">.” </font></span></div></div></div></div></div></div></blockquote></div></div></div></div></blockquote></div></div></div></div></div></blockquote></div></div></blockquote></div><div class=""><div class="gmail_extra"><div class="gmail_quote"><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;"><div class="" style="word-wrap: break-word;"><div class=""><div class="h5"><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><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;"><div class="" style="word-wrap: break-word;"><div class=""><div class=""><div class=""><div class=""><div class=""><span class="" style="background-color: rgb(255, 255, 255);"><font color="#333333" class=""><br class=""></font></span></div></div></div></div></div></div></blockquote></div></div></div></div></blockquote></div></div></div></div></div></blockquote></div></div></div><div class="">Kind Regards</div><div class="">TedvG </div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 12 Oct 2016, at 19:00, Austin Zheng <<a href="mailto:austinzheng@gmail.com" class="">austinzheng@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">This is utterly ridiculous. Chris Lattner and the other core team members posted repeatedly at the beginning of the Swift 3.x/4 development cycle asking us expressly to keep the discussion focused on a number of specific topics. Not only have you repeatedly ignored that request, now you are being condescending and rude to a community member who has put in tremendous effort over the last few months trying to make swift-evolution a better place. Please consider whether or not disregarding the core team's wishes in this matter is really the best way to show respect for the community and the project.<div class=""><br class=""></div><div class="">Best regards,</div><div class="">Austin</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Oct 12, 2016 at 9:54 AM, Ted F.A. van Gaalen 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">Dear Xiaoid</div>I still don’t agree with you, there should be some flexibility, things should live<div class="">and also, if we adhere to this list you refer to on Github, than no new</div><div class="">topics would be discussable...</div><div class="">I am sorry if I wrote a bit harsh to you.</div><div class="">Kind Regards </div><div class=""><pre class="m_-8905701175066207869tw-ta m_-8905701175066207869tw-text-large m_-8905701175066207869tw-data-text" id="m_-8905701175066207869tw-target-text" style="border:none;padding:0px 0.14em 0px 0px;margin-top:0px;font-family:inherit;overflow:hidden;width:281.5px;white-space:pre-wrap;word-wrap:break-word;height:72px;font-size:48px!important;line-height:72px!important;color:rgb(33,33,33)!important"><span lang="zh-CN" class="">尊敬的</span></pre><span class="HOEnZb"><font color="#888888" class=""><div class=""><br class=""></div></font></span></div><span class="HOEnZb"><font color="#888888" class=""><div class="">Ted</div></font></span><div class=""><div class="h5"><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 12 Oct 2016, at 18:41, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" target="_blank" class="">xiaodi.wu@gmail.com</a>> wrote:</div><br class="m_-8905701175066207869Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><div class="gmail_extra"><div class="gmail_quote">On Wed, Oct 12, 2016 at 11:32 AM, Ted F.A. van Gaalen<span class="m_-8905701175066207869Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:tedvgiosdev@gmail.com" target="_blank" class="">tedvgiosdev@gmail.com</a>></span><span class="m_-8905701175066207869Apple-converted-space"><wbr class=""> </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"><div style="word-wrap:break-word" class="">Hi Xiaodi,<div class="">please read in-line, thank you.</div><div class=""><br class=""></div><div class=""><div class=""><blockquote type="cite" class=""><span class=""><div class="">On 12 Oct 2016, at 15:58, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" target="_blank" class="">xiaodi.wu@gmail.com</a>> wrote:</div><br class="m_-8905701175066207869m_4462182378981150637Apple-interchange-newline"></span><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><span class="">On Wed, Oct 12, 2016 at 7:47 AM, Ted F.A. van Gaalen<span class="m_-8905701175066207869Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:tedvgiosdev@gmail.com" target="_blank" class="">tedvgiosdev@gmail.com</a>></span><span class="m_-8905701175066207869Apple-converted-space"><wbr class=""> </span>wrote:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word" class=""><br class=""><div class=""><span class="m_-8905701175066207869m_4462182378981150637gmail-"><blockquote type="cite" class=""><div class="">On 11 Oct 2016, at 23:04, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" target="_blank" class="">xiaodi.wu@gmail.com</a>> wrote:</div><br class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350Apple-interchange-newline"><div class="">Reflection is likely to be tackled in Swift 5, no?</div></blockquote><br class=""></span><div class="">I'd think you don’t need reflection that much, because defining</div><div class="">dynamic classes (and other entities) are solely incremental compiler</div><div class="">tasks, for which it can use previously compiled meta reference</div><div class="">information (xref symbols etc). </div><div class=""><br class=""></div><div class="">Imho in that perspective it is more or less independent</div><div class="">of reflection. Reflection is as far as I can see is more intended to offer </div><div class="">meta information at the programming level.? </div><span class="m_-8905701175066207869m_4462182378981150637gmail-"><div class=""><br class=""></div><blockquote type="cite" class=""><div class="">So realistically, this could be on track for Swift 6 or 7.</div></blockquote><br class=""></span>As already written, there is no timeframe/deadline for this idea, it is just an idea, </div><div class="">not a proposal (yet).</div><span class="m_-8905701175066207869m_4462182378981150637gmail-"><div class=""><div class=""><br class=""><blockquote type="cite" class="">Let's postpone discussion until then.<br class=""></blockquote><div class=""><br class=""></div></div></div></span><div class="">Feel free to do so, but why postponing having ideas and discussing them?</div></div></blockquote><div class=""><br class=""></div></span><div class="">The core team has requested that discussions be focused on the priorities identified for the current phase of Swift 4. There's a sound rationale for this request. Per Chris: "<span style="white-space:pre-wrap" class="">The community benefits from keeping focus on a limited number of topics, because if there is too much going on, no one can follow and keep track of it all. It is important for the core team to be involved in key discussions up front. In the Swift 3 cycle, it was problematic that many folks had no time to follow the threads until after the review period completed.”</span></div></div></div></div></div></blockquote><div class=""><br class=""></div><div class="">You are pulling the above out of context hereunder: </div><span class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""><span style="white-space:pre-wrap" class=""><br class=""></span></div><div class=""><font class=""><span style="white-space:pre-wrap" class="">I'm sure many people have ideas about dynamic facilities in Swift, as do we all about other ideas, and many have been trying to be respectful of this new proposed process. I think we can all agree that maximum participation and the best solutions are most likely when everyone stays on the same page with regard to the process by which we go about these discussions. No need to postpone having ideas about Swift or talking about them with your friends and colleagues, but let's respect the core team's urging to postpone discussing them on this particular list for the reasons identified above.</span></font></div><div class=""><br class=""></div></div></div></div></div></blockquote></span><div class="">1. You are not a member of the core team, far from it, sorry.</div><div class=""> Don’t think for them, they can do that quite well themselves. and thus: </div></div></div></div></blockquote><div class=""><br class=""></div><div class="">I'm not trying to speak for the core team; sorry if I'm giving off that impression.</div><div class=""> </div><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"><div style="word-wrap:break-word" class=""><div class=""><div class=""><div class="">2. If the core team would have problems with me bringing forward this topic, </div><div class=""> <span class="m_-8905701175066207869Apple-converted-space"> </span>they might/will inform me that this is undesired, in that case I’ll stop writing about it. </div></div></div></div></blockquote><div class=""><br class=""></div><div class="">As a member of the community, I'm voicing *my* concern that this is not an opportune time to discuss this topic. It's up to all participants, not just the core team, to try to make sure that the evolution process works effectively. So far, in the context of other threads, other community members have also been active in pointing out when topics stray too far from the suggested areas of focus. I think this is good practice and I'm trying to contribute to that effort.</div><div class=""><br class=""></div><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"><div style="word-wrap:break-word" class=""><div class=""><div class=""><div class="">3. My current subject is an extension spin-off from the topic “associated objects”, wherein</div><div class=""> <span class="m_-8905701175066207869Apple-converted-space"> </span>“extending the language" is discussed. Meta Programming and Adding Dynamic Features to Swift </div><div class=""> <span class="m_-8905701175066207869Apple-converted-space"> </span>are currently strongly in focus and is surely one of the most important things to bring to Swift in the near future!</div></div></div></div></blockquote><div class=""><br class=""></div><div class="">I'm sorry, but this is not true. The list of focus topics for this phase of Swift is on the swift-evolution GitHub project readme, and this is not one of them.</div><div class=""><br class=""></div><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"><div style="word-wrap:break-word" class=""><div class=""><div class=""><div class="">4. read this on <a href="http://swift.org/" target="_blank" class="">Swift.org</a>: </div><div class=""><h3 id="m_-8905701175066207869m_4462182378981150637proposing-new-features" style="box-sizing:border-box;margin:0px 0px 0.5em;padding:1em 0px 0px;font-weight:400;line-height:1;color:rgb(51,51,51)" class=""><span style="font-size:12px" class="">"Proposing New Features"</span></h3><p style="box-sizing:border-box;margin:0px 0px 1.5em;padding:0px;color:rgb(51,51,51)" class="">"New features or directions for the Swift language can come from anyone with a good idea."</p><p style="box-sizing:border-box;margin:0px 0px 1.5em;padding:0px;color:rgb(51,51,51)" class="">"Open discussion and iteration over the ideas in a public forum is essential to reaching the best possible solutions."</p><div class="">also </div><div class=""><br class=""></div><div class=""><span style="color:rgb(51,51,51);background-color:rgb(255,255,255)" class="">"Everyone is welcome to propose, discuss, and review ideas to improve the Swift language and standard library on the </span><a href="https://swift.org/community/#swift-evolution" title="Swift evolution mailing list" style="box-sizing:border-box;color:rgb(64,120,192);text-decoration:none" target="_blank" class="">swift-evolution mailing list</a><span style="background-color:rgb(255,255,255)" class=""><font color="#333333" class="">.” </font></span></div><div class=""><span style="background-color:rgb(255,255,255)" class=""><font color="#333333" class=""><br class=""></font></span></div><div class=""><br class=""></div><div class=""><br class=""></div></div><div class="">5. If a certain topic is not interesting for you personally then simply ignore it and don’t react.</div></div></div></div></blockquote><div class=""><br class=""></div><div class="">That is not what I'm saying. I'm very interested in this topic. However, I'm concerned that neither I nor others with intense interest can contribute meaningfully at this phase, because the suggested focus for the moment is not on this topic. I would not want to ignore the topic at all.</div><div class=""> </div><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"><div style="word-wrap:break-word" class=""><div class=""><div class=""><div class="">6. Well meant advice: be a little less lofty,</div><div class=""> </div><div class=""><br class=""></div><div class="">Kind Regards </div><div class="">TedvG</div><div class=""><div class="m_-8905701175066207869h5"><div class=""><br class=""></div><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">In this case for instance, thinking about dynamic facilities, will presumably </div><div class="">also influence thinking about reflection and vice versa. </div><div class="">Thinking “wider” and “further” broadens the horizon of course.</div><div class="">For example. what about a compiler/interpreter self improving based on artificial intelligence? is this 2016? </div><div class="">So one can (should) do both: that is think in small steps, like discussing</div><div class="">“just” language elements and at the same time have an eye (or two) for the </div><div class="">broader picture. If one concentrates too much on the direct path in front, one might</div><div class="">not see other paths or what lays further ahead, which limits progress. </div><div class=""><br class=""></div><div class="">————————————————</div><div class="">Let me write a small cartoon here, just intended as a little bit of humour just to illustrate this:</div><div class=""><br class=""></div><div class="">A few thousand years ago, two very nice beings ( just returned from attending a</div><div class="">very primitive and awkward election debate, still shivering), looking at a pair </div><div class="">of fairly round stone slabs with a hole in the centre.</div><div class=""><br class=""></div><div class="">“What’s this ?, Why round? why the holes? Nice job, but what is it? Is it art?”</div><div class=""><br class=""></div><div class="">“Errrrhmm, well.. I might call it ‘Wheelz', not sure yet, you can use two of more of them</div><div class="">underneath or aside of things you’d like to move around more easily…</div><div class="">with less friction, which was a hell of a drag anyway."</div><div class=""><br class=""></div><div class="">The other guy walks around it, apparently deeply thinking about it. </div><div class="">after some silence he says:</div><div class="">“Aha… hmm.. well.. Oh, i see, yeah, yep, that’s kinda cool.. might be useful. </div><div class="">But let’’s postpone discussing it until ball-bearings have been invented. “</div><div class="">————————————————</div><div class=""><br class=""></div><div class="">hmmm, I really have too much time… :o)</div><div class=""><br class=""></div><div class="">Kind Regards</div><span class="m_-8905701175066207869m_4462182378981150637gmail-HOEnZb"><font color="#888888" class=""><div class="">Ted</div></font></span><span class="m_-8905701175066207869m_4462182378981150637gmail-"><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""> </div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><br class=""><blockquote type="cite" class=""><div class=""><br class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Tue, Oct 11, 2016 at 15:59 David Sweeris via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="auto" class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg"><div class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg"><br class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg"></div><div class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg">On Oct 11, 2016, at 12:40, Anton Zhilin via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" target="_blank">swift-evolution@swift.org</a>> wrote:<br class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg"><br class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg"></div><blockquote type="cite" class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg"><div dir="ltr" class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg"><div class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227markdown-here-wrapper"><p class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" style="margin:0px 0px 1.2em">Hello Ted,<br class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg">First of all, this topic belongs to reflection, which is specifically stated to be out of scope of Swift 4 Phase 1. So all considerations are purely theoretical for now.<br class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg">That said, I also thought about this problem. The best I could imagine is something along the following lines:</p><pre class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" style="font-family:consolas,inconsolata,courier,monospace;font-size:1em;line-height:1.2em;margin:1.2em 0px"><code class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227language-swift m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" style="font-size:0.85em;font-family:consolas,inconsolata,courier,monospace;margin:0px 0.15em;white-space:pre-wrap;overflow:auto;border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;border:1px solid rgb(204,204,204);padding:0.5em;color:rgb(51,51,51);background-color:rgb(248,248,248);display:block;background-position:initial initial;background-repeat:initial initial"><span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-keyword" style="color:rgb(51,51,51);font-weight:bold">var</span> builder = <span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-type m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" style="color:rgb(68,85,136);font-weight:bold">StructBuilder</span>(name: <span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-string" style="color:rgb(221,17,68)">"Person"</span>)
builder.addProperty(name: <span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-string" style="color:rgb(221,17,68)">"name"</span>, type: <span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-type m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" style="color:rgb(68,85,136);font-weight:bold">String</span>.<span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-keyword" style="color:rgb(51,51,51);font-weight:bold">self</span>)
builder.addProperty(name: <span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-string" style="color:rgb(221,17,68)">"age"</span>, type: <span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-type m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" style="color:rgb(68,85,136);font-weight:bold">Int</span>.<span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-keyword" style="color:rgb(51,51,51);font-weight:bold">self</span>)
builder.addComputedProperty(na<wbr class="">me: <span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-string" style="color:rgb(221,17,68)">"description"</span>, getter: { (this: <span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-type m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" style="color:rgb(68,85,136);font-weight:bold">Any</span>) -> <span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-type m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" style="color:rgb(68,85,136);font-weight:bold">String</span> <span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-keyword" style="color:rgb(51,51,51);font-weight:bold">in</span> ... })
builder.addComformance(<span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-type m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" style="color:rgb(68,85,136);font-weight:bold">CustomS<wbr class="">tringConvertible</span>.<span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-keyword" style="color:rgb(51,51,51);font-weight:bold">self</span>)
<span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-keyword" style="color:rgb(51,51,51);font-weight:bold">let</span> type: <span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-type m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" style="color:rgb(68,85,136);font-weight:bold">Any</span>.<span class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350m_-1272261771439787227hljs-type m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" style="color:rgb(68,85,136);font-weight:bold">Type</span> = builder.build()
</code></pre><p class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" style="margin:0px 0px 1.2em">Obviously, to interact with such dynamic types and their objects, we need the whole working reflection system that we don’t have right now.</p></div></div></blockquote></div><div dir="auto" class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg">I *think* that's only true for non-generic code, and types that aren't subclasses... I think...<div class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg"><br class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg"></div><div class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg">Anyway, I'm starting to wonder if some code I'm trying to write might be impossible without either this feature, or some/all of the stuff from the generics manifesto. So put me down as, in principle, a strong +1 (pending details of the proposal when it actually gets written for Swift 10).</div><div class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg"><br class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg"></div><div class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg">- Dave Sweeris </div></div>______________________________<wbr class="">_________________<br class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg">swift-evolution mailing list<br class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg"><a href="mailto:swift-evolution@swift.org" class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg"><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="m_-8905701175066207869m_4462182378981150637gmail-m_-5180192693485377350gmail_msg" target="_blank">https://lists.swift.org/mailma<wbr class="">n/listinfo/swift-evolution</a></blockquote></div></div></blockquote></div></span></div></blockquote></div></div></div></div></blockquote></div></div></div></div></div></blockquote></div></div></div></div></blockquote></div><br class=""></div></div></div></div><br class="">______________________________<wbr class="">_________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" 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/<wbr class="">mailman/listinfo/swift-<wbr class="">evolution</a><br class="">
<br class=""></blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></body></html>