<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>I'm finding it really hard to see the advantage of this proposal with out reconciling the possibility of .self going away. I think this should be postponed after .self is reviewed in swift 4. Premature optimization imo. </div><div><br>On Jul 22, 2016, at 3:20 PM, David Hart via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>Where do these double generics come from? Never saw them...</div><div><br>On 22 Jul 2016, at 17:54, Anton Zhilin <<a href="mailto:antonyzhilin@gmail.com">antonyzhilin@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2016-07-22 18:51 GMT+03:00 David Hart <span dir="ltr"><<a href="mailto:david@hartbit.com" target="_blank">david@hartbit.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div><div style="direction:inherit">Isn't the solution to a lot of these issues allowing explicit generalization instead of this meta type business?</div></div></div></blockquote><div><br></div><div>And what would you suggest for "double generics" in initializers?</div><div>ExampleType<Int><Double>() // not good</div></div></div></div>
</div></blockquote></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>