<div dir="ltr">Hi Marco,<div><br></div><div>Is there proper documentation for Swift open source? Is there design documents for the n-lines of code? Is there some clear commenting for every line of code? </div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Thanks!</div><div><br></div><div>Best,</div><div><br></div><div>Shyamal Chandra</div><div><a href="mailto:shyamalc@gmail.com" target="_blank">shyamalc@gmail.com</a></div><div>Linkedin: <a href="http://www.linkedin.com/in/shyamalc" target="_blank">http://www.linkedin.com/in/shyamalc</a></div><div>Phone: 620-719-9064</div></div></div></div>
<br><div class="gmail_quote">On Tue, Sep 13, 2016 at 9:22 PM, Marco S Hyman <span dir="ltr"><<a href="mailto:marc@snafu.org" target="_blank">marc@snafu.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sep 13, 2016, at 6:53 PM, Shyamal Chandra via swift-users <<a href="mailto:swift-users@swift.org">swift-users@swift.org</a>> wrote:<br>
><br>
> I am not arguing; I am bringing up defect in the Apple way of handling bugs for Swift, Xcode, and Playgrounds. Am I supposed to wait for eternity?<br>
<br>
</span>As Jens noted, you have to separate Swift from Xcode and Playgrounds. With respect to Swift you’ve three choices.<br>
<br>
1) do nothing and wait<br>
2) dig in and fix the problem yourself<br>
3) throw some money at someone else who will dig in and fix the problem.<br>
<br>
When it comes to bugs and missing features in open source projects I’ve done all of the above at various times. For a minor annoyance I wait. If the bug/missing feature is something that is within my area of expertise I dig in and fix. If it is something I have to have but don’t have the knowledge nor the time to gain the knowledge I’ve funded others to dig in and fix.<br>
<br>
Which are you going to do?</blockquote></div><br></div>