<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div><br>On Jul 29, 2016, at 09:30, Karl 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"><br class=""><div><blockquote type="cite" class=""><div class="">On 29 Jul 2016, at 18:01, Brandon Knope 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=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I think this just shows how familiar many of us are with this process.<div class=""><br class=""></div><div class="">It’s fun and challenging coming up with the great ideas…but someone has to implement it. It may not be fun…and it may be very time consuming.</div><div class=""><br class=""></div><div class="">I think a lot of us just expected the core team to implement these all…but they really need help from the community to save them time and sanity with trying to get all of this done.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">To me this means I need to familiarize myself with the swift code base even more. I need to understand all the GitHub processes to get a change implemented and submitted.</div><div class=""><br class=""></div><div class="">I really hope at some point someone can make a primer of the process they went through to implement one of these proposals from start to finish. I think this could be illuminating for many on this list.</div><div class=""><br class=""></div><div class="">ALSO: I think this is where a forum can help greatly: some of us need a way to discuss our implementations and ask for help while we are working on one of these proposals. Mailing lists make it very hard to have a general discussion where we talk code and ask for help in get detail. It is also much easier for others to browse to learn from that conversation.</div><div class=""><br class=""></div><div class="">In short: the swift-evolution process works…but some of us in the community need to step up and help a little more other than just proposing things. I think the swift team could make this easier with some detailed guides and documentation and a forum for better discussions when trying to implement these things…but I know they are insanely busy. I do think some time investment in this area will pay off in the future…and quickly.</div><div class=""><br class=""></div><div class="">Brandon</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jul 29, 2016, at 11:15 AM, Félix Cloutier 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=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hello all,<div class=""><br class=""></div><div class="">With the Swift 3 deadline passed, according to the Swift Evolution progress page, about 20% of the proposals that the community voted in won't make it for Swift 3. Beyond the implications for the language itself, what does that mean for the swift-evolution process?<br class=""><div class="">
<br class="Apple-interchange-newline"><span style="font-family: 'Lucida Grande'; font-size: 12px; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Félix</span>
</div>
<br class=""></div></div>_______________________________________________<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" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""></div></div>_______________________________________________<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">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""><div class="">The thing that’s stopping me contributing to the compiler itself is that it uses LLVM types and functions, and I don’t know them. The Swift compiler itself looks very clean and approachable.</div><div class=""><br class=""></div><div class="">And then, when you try to look up any of those LLVM functions, you get Doxygen, which isn’t really great. It just puts me off really getting to grips with LLVM’s conventions. Maybe one day when I have more time.</div><div class=""><br class=""></div><div class="">Unless somebody knows of some better documentation?</div></div></blockquote><div><br></div>This is a good reference if you want to start getting to know things like DenseMap, SmallVector, etc.: <a href="http://llvm.org/docs/ProgrammersManual.html#picking-the-right-data-structure-for-a-task">http://llvm.org/docs/ProgrammersManual.html#picking-the-right-data-structure-for-a-task</a><div><br></div><div>The other thing I would suggest is just taking a look at the headers and when needed the source. Most of the ADTs closely resemble STL counterparts in API and are easy to get up-to-speed with. </div><div><br></div><div>I have never taken a serious look at the Doxygen documentation as I personally don't find it useful with the source available. </div><div><br></div><div>Mark</div><div><br><blockquote type="cite"><div><div class=""><br class=""></div><div class="">Karl</div></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></div></body></html>