<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div style="direction: inherit;"><br></div><div style="direction: inherit;">Some ones proposal have always been accepted very quickly even though it is not fully discussed.</div><div style="direction: inherit;"><br></div></div><div>I don't know why.</div><div><br></div><div>so if some one always focus on swift-evolution then it has more priority to proposal?</div><div><br></div><div>What about others?</div><div><br></div><div>I proposal this since February, May. no one said it is a problem. But in June, some one lead an idea of & and union type proposal has been listed in not-welcomed proposal for Swift 3.<b> No one notify me that discussion and no one discussed that with me</b>. I try to discuss with the core team but they have no response before June. But After June, they said it is not for Swift 3. OK, I proposed for Swift 4, and get a shit response. </div><div><br></div><div>Email list let proposal topic hide themselves?</div><div><br></div><div>No direct answer of my Feb, May proposal, but a June discussed sometime somewhere I don't know.</div><div><br></div><div>so I make a proposal, and this is the result.</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div>在 2016年8月11日，21:42，Wallacy <<a href="mailto:wallacyf@gmail.com">wallacyf@gmail.com</a>> 写道：<br><br></div><blockquote type="cite"><div><div dir="ltr"><div>You don't need to act like a jerk. It's really difficult ask to you follow the past discussions?</div><div><br></div><div>Compositions type are "generally" well accepted for this community, but has some problems to be solved first.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">Em qui, 11 de ago de 2016 às 02:53, Cao, Jiannan via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div><span style="font-family:Helvetica,'Microsoft Yahei',verdana">OK. I'll shut up since I waste your time.</span></div><div><br></div>At 2016-08-11 13:41:59, "Chris Lattner" <<a href="mailto:clattner@apple.com" target="_blank">clattner@apple.com</a>> wrote:<br> <blockquote style="PADDING-LEFT:1ex;MARGIN:0px 0px 0px 0.8ex;BORDER-LEFT:#ccc 1px solid">You’re certainly welcome to your opinion. <div><br></div><div>Swift is not Typescript, and this topic has been discussed extensively in the past. We expect you to familiarize yourself with those discussions. Otherwise, it is just a waste of people’s time to rehash old arguments.<div><br></div><div>-Chris</div><div><br><div><blockquote type="cite"></blockquote></div></div></div></blockquote></div><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><blockquote style="PADDING-LEFT:1ex;MARGIN:0px 0px 0px 0.8ex;BORDER-LEFT:#ccc 1px solid"><div><div><div><blockquote type="cite"><div>On Aug 10, 2016, at 10:22 PM, Cao, Jiannan <<a href="mailto:frogcjn@163.com" target="_blank">frogcjn@163.com</a>> wrote:</div><br></blockquote></div></div></div></blockquote></div><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><blockquote style="PADDING-LEFT:1ex;MARGIN:0px 0px 0px 0.8ex;BORDER-LEFT:#ccc 1px solid"><div><div><div><blockquote type="cite"><div><div style="line-height:1.7;font-size:14px;font-family:Arial"><div>Swift evolution seems not an evolution. </div><div><br></div><div>I'll leave this mail list since this is not a good proposal environment. Typescript and other language community is more open to new idea. Swift-evolution is just a weird community. </div><div style="zoom:1"></div><div></div><div><br></div></div></div></blockquote></div></div></div></blockquote></div><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><blockquote style="PADDING-LEFT:1ex;MARGIN:0px 0px 0px 0.8ex;BORDER-LEFT:#ccc 1px solid"><div><div><div><blockquote type="cite"><div><div style="line-height:1.7;font-size:14px;font-family:Arial">在 2016-08-11 13:18:54，"Chris Lattner" <<a href="mailto:clattner@apple.com" target="_blank">clattner@apple.com</a>> 写道：<br> </div></div></blockquote></div></div></div></blockquote></div><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><blockquote style="PADDING-LEFT:1ex;MARGIN:0px 0px 0px 0.8ex;BORDER-LEFT:#ccc 1px solid"><div><div><div><blockquote type="cite"><div><div style="line-height:1.7;font-size:14px;font-family:Arial"><blockquote style="PADDING-LEFT:1ex;MARGIN:0px 0px 0px 0.8ex;BORDER-LEFT:#ccc 1px solid"><br><div><blockquote type="cite"><div>On Aug 10, 2016, at 8:15 PM, Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br><div>I don't know if the core team feels differently now with respect to Swift 4, but union types are listed as a "commonly rejected change":<br><br><a href="https://github.com/apple/swift-evolution/blob/master/commonly_proposed.md" target="_blank">https://github.com/apple/swift-evolution/blob/master/commonly_proposed.md</a><br></div></blockquote></div><br><div>There is no change in opinion here. This topic is also out of scope for Swift 4 stage 1 in any case.</div><div><br></div><div>-Chris</div></blockquote></div></div></blockquote></div></div></div></blockquote></div><br><br><span title="neteasefooter"><p> </p></span>_______________________________________________<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>
</blockquote></div>
</div></blockquote></body></html>