<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Nov 1, 2016, at 9:50 PM, Shyamal Chandra <<a href="mailto:shyamalc@gmail.com" class="">shyamalc@gmail.com</a>> wrote:<div><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">Hi Chris,<div class=""><br class=""></div><div class="">First of all, there is tremendous instability with Xcode Playgrounds. </div></div></div></blockquote><div><br class=""></div><div>Hi Shyamal,</div><div><br class=""></div><div>The vast majority of the instability of playgrounds is a result of the compiler code which is already open source. I look forward to you sending in patches to improve Swift: if you’re looking for a good starting place, there are a large number of submitted bugs in JIRA which we’d love your help on, and a large number of known crashers tracked in the validation suite.</div><div><br class=""></div><div>-Chris</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">I paste the same simple code into Xcode Playgrounds; sometimes, it works and sometimes, it doesn't work. Why don't you make the Playgrounds open source so I can investigate? You should tell this to Tim Cook as soon as possible. I wanted to add Swift to the list of languages in Juypter for workbook usage. If a project is closed-source, I cannot do anything without looking at documented code. The documentation for Xcode Playgrounds is not there. For the XCPlayground library, there is just an API call reference that is sparsely documented. I can wait for infinity for a response on the forums but Apple should provide better support rather than charging money for each technical support call. This is disappointing since Apple was founded to make computing easy, not hard on purpose, making code writing a black art.</div><div class="gmail_extra"><br clear="all" class=""><div class=""><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class="">Thanks!</div><div class=""><br class=""></div><div class="">Best,</div><div class=""><br class=""></div><div class="">Shyamal Chandra</div><div class=""><a href="mailto:shyamalc@gmail.com" target="_blank" class="">shyamalc@gmail.com</a></div><div class="">Linkedin: <a href="http://www.linkedin.com/in/shyamalc" target="_blank" class="">http://www.linkedin.com/in/shyamalc</a></div><div class="">Phone: 620-719-9064</div></div></div></div>
<br class=""><div class="gmail_quote">On Tue, Sep 13, 2016 at 10:56 PM, Chris Lattner <span dir="ltr" class=""><<a href="mailto:clattner@apple.com" target="_blank" class="">clattner@apple.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><span class="">On Sep 13, 2016, at 5:34 PM, Shyamal Chandra <<a href="mailto:shyamalc@gmail.com" target="_blank" class="">shyamalc@gmail.com</a>> wrote:</span><div class=""><span class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">Hi Chris,<div class=""><br class=""></div><div class="">Here is a forum question that I posted a while back. The latest post says to file a bug under the bug report. </div></div></div></blockquote></span><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><span class=""><div class="">Here's the post:</div><div class=""><br class=""></div><div class=""><a href="https://forums.developer.apple.com/thread/61953" target="_blank" class="">https://forums.developer.<wbr class="">apple.com/thread/61953</a> (Playgrounds error)</div></span></div></div></blockquote><div class=""><br class=""></div><div class="">Thanks for the link. Contrary to your claims, it appears that you promptly got a response from an Apple employee, and it appears that you didn’t follow his instructions to file a radar in <a href="http://bugreporter.apple.com/" target="_blank" class="">bugreporter.apple.com</a>.</div><div class=""><br class=""></div><div class="">Now that Xcode 8 has shipped to the Mac App Store today, I’d suggest you download that and try it. There are a number of bugs that are fixed between beta 6 and the final release, and that may include this one.</div><span class=""><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">I was doing something "simple" in Playgrounds and my version of Playgrounds doesn't function properly because it is emitting an error when I write bug-free code. Why is Playgrounds so flaky? Sometimes, it shows the output on the right side; sometime, it doesn’t.</div></div></div></blockquote><div class=""><br class=""></div></span><div class="">Two simple and obvious answers come to mind: you are running advertised-as-beta software, and even shipping software does have bugs.</div><span class=""><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class="">I have had mixed success with the bug reporter tool from Apple; most of the time, they ask for the system diagnostics and then, tell you to update your version. Sometimes, they just close the issue and nothing happens.</div></div></blockquote></div><div class=""><br class=""></div></span><div class="">I understand that you claim to have had problems with Radar/<a href="http://bugreporter.apple.com/" target="_blank" class="">bugreporter.apple.com</a>, but again I can see no evidence of you ever filing a bug in it (and you haven’t provided me any radar numbers to cross reference), so there isn’t much I can do to help you. Needless to say, we do actually need the system diagnostics in order to reproduce issues like this, as you found on the forum, your issue doesn’t reproduce trivially for other folks.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Finally, as others have pointed out, your approach on this thread hasn’t been particularly constructive. Despite your apparent expectation, Apple has not signed up to fix any and every bug reported against Swift. That said, we all want to build a strong community, and if you are interested in working in a helpful and productive way we would love for you to be part of that community. On the other hand, if you find that Swift on Linux isn’t ready for you today and that you don’t want to invest effort in it, then perhaps it is best for you to come back at some point later in the future.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class=""><br class=""></div><div class="">-Chris</div><span class=""><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="gmail_extra"><br clear="all" class=""><div class=""><div class="m_-2309442243137361509gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class="">Thanks!</div><div class=""><br class=""></div><div class="">Best,</div><div class=""><br class=""></div><div class="">Shyamal Chandra</div><div class=""><a href="mailto:shyamalc@gmail.com" target="_blank" class="">shyamalc@gmail.com</a></div><div class="">Linkedin: <a href="http://www.linkedin.com/in/shyamalc" target="_blank" class="">http://www.linkedin.com/in/<wbr class="">shyamalc</a></div><div class="">Phone: <a href="tel:620-719-9064" value="+16207199064" target="_blank" class="">620-719-9064</a></div></div></div></div>
<br class=""><div class="gmail_quote">On Tue, Sep 13, 2016 at 7:02 PM, Chris Lattner <span dir="ltr" class=""><<a href="mailto:clattner@apple.com" target="_blank" class="">clattner@apple.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sep 12, 2016, at 3:03 PM, Shyamal Chandra via swift-users <<a href="mailto:swift-users@swift.org" target="_blank" class="">swift-users@swift.org</a>> wrote:<br class="">
</span><span class="">> Hope you are doing well!<br class="">
><br class="">
> Swift is very volatile language that keeps on changing with every new version of Xcode. When you are trying to run old code with different syntax, you run into problems because the code is no longer compatible. Instead of moving onto Swift 3, 4, and 5 (with different syntax), why don't you standardize the library and language operations and functions for the different package and frameworks included with Xcode<br class="">
<br class="">
</span>The subject line of this message seems like it is intended to be provocative, not helpful.<br class="">
<br class="">
Despite that, you’ll be happy to know that the goal of Swift 4 is to be source compatible with Swift 3, so the concerns that you are complaining about are historic, not future problems.<br class="">
<span class=""><br class="">
> because I have already submitted multiple bugs to the bug report that are with the official release of Xcode and I am very disappointed with the software quality.<br class="">
<br class="">
</span>I don’t see any radars filed by you in the system, but perhaps they are just under a different name. In any case, thank you for filing bugs, we do read and care about them! Please send me the radar numbers (off list if you prefer) and I’ll take a look.<br class="">
<span class="m_-2309442243137361509HOEnZb"><font color="#888888" class=""><br class="">
-Chris<br class="">
<br class="">
</font></span></blockquote></div><br class=""></div></div>
</div></blockquote></span></div><br class=""></div></blockquote></div><br class=""></div></div>
</div></blockquote></div><br class=""></body></html>