<div dir="ltr"><div class="markdown-here-wrapper" style=""><p style="margin:0px 0px 1.2em!important">I think that <code style="font-size:0.85em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-radius:3px;display:inline">"we don't have time to implement this time-saving project-accelerating quality-improving thing"</code> is widely recognised as an anti-pattern (or anti-process if that’s a thing) these days, and I’d hope Apple would find a way to avoid this problem. :)<br></p>
<div title="MDH:SSB0aGluayB0aGF0IGAid2UgZG9uJ3QgaGF2ZSB0aW1lIHRvIGltcGxlbWVudCB0aGlzIHRpbWUt
c2F2aW5nIHByb2plY3QtYWNjZWxlcmF0aW5nIHF1YWxpdHktaW1wcm92aW5nIHRoaW5nImAgaXMg
d2lkZWx5IHJlY29nbmlzZWQgYXMgYW4gYW50aS1wYXR0ZXJuIChvciBhbnRpLXByb2Nlc3MgaWYg
dGhhdCdzIGEgdGhpbmcpIHRoZXNlIGRheXMsIGFuZCBJJ2QgaG9wZSBBcHBsZSB3b3VsZCBmaW5k
IGEgd2F5IHRvIGF2b2lkIHRoaXMgcHJvYmxlbS48YnI+" style="height:0;width:0;max-height:0;max-width:0;overflow:hidden;font-size:0em;padding:0;margin:0"></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, 14 Aug 2017 at 21:44 Jacob Williams <<a href="mailto:ponyboy47@gmail.com">ponyboy47@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">A Swift developer has actually started a blog series about the swift compiler. The links to his post were posted in one of the evolution topics a little while ago. The series is incomplete, but it gives a lot of explanations about the various parts of the swift compiler.<div><br></div><div><a href="https://medium.com/@slavapestov/the-secret-life-of-types-in-swift-ff83c3c000a5" target="_blank">https://medium.com/@slavapestov/the-secret-life-of-types-in-swift-ff83c3c000a5</a></div><div><a href="https://medium.com/@slavapestov/how-to-talk-to-your-kids-about-sil-type-use-6b45f7595f43" target="_blank">https://medium.com/@slavapestov/how-to-talk-to-your-kids-about-sil-type-use-6b45f7595f43</a></div><div><br></div><div>I wholeheartedly agree that a mentorship program would be extremely useful for helping others get up-to-speed with the swift compiler. I myself wished I understood it better. The only problem is that with something so large and complex, it would take a lot of time and effort to document and create a tutorial for it. I wish that this would happen, but I don’t know that anyone at Apple has the time and there probably aren’t very many people outside of apple with the know-how and time to write a tutorial as a hobby. I hope that I’m wrong though.</div><div><br></div><div><br><div><blockquote type="cite"></blockquote></div></div></div><div style="word-wrap:break-word"><div><div><blockquote type="cite"><div>On Aug 14, 2017, at 2:35 PM, Jay Abbott via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br class="m_8209402617302505040Apple-interchange-newline"></blockquote></div></div></div><div style="word-wrap:break-word"><div><div><blockquote type="cite"><div><div dir="ltr"><div>I think we should have some kind of mentorship program for the swift source. I'm confident that my following statement doesn't apply to just me:<br><br>"I'd
love to get involved in the source a lot more, and my previous efforts
to browse around and understand it a bit better have been thwarted by
lack of time, a specific goal/direction, and no proper commitment (all
my own failings of course). I'd be happy to learn the code and
implement proposals, but I really want someone to turn to when I need
some help and guidance."<br><br>In addition to the core team, I think there are a few others who know the code well enough, and who may be willing to mentor and
share that knowledge further. Having a specific mentor makes it much easier to get to a level where you feel comfortable talking to the wider development community on swift-dev for example.<br><br>There would need to be some level of self-starting bar, which would need to be supported by some documentation to read, and some simple tasks/tutorials to complete (For example create a branch which removes an existing feature and a tutorial to re-implement it, that touches a few key areas of the code-base). The swift project and the evolution process would benefit by having more potential implementors, so writing such documentation and getting-started guides should be a high priority in order to help people get more involved. Once complete, it would be great to choose a proposal, find a mentor, and start work on it under their guidance.<br><br>I believe effort focused in this area will have a high return, given the high quality and quantity of passion and talent I see in this list.<br></div></div></div></blockquote></div></div></div><div style="word-wrap:break-word"><div><div><blockquote type="cite"><div>
_______________________________________________<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" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></div></blockquote></div></div></div></blockquote></div>