<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 13, 2016, at 5:34 PM, Shyamal Chandra via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-family: Alegreya-Regular; font-size: 15px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Here is a forum question that I posted a while back. The latest post says to file a bug under the bug report. 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><br class=""></div><div>Apple’s bug-reporting process is not the greatest, I agree. Most of that is a side effect of how secretive and opaque Apple is: you can’t see bugs anyone else has filed, and once you file a bug you can’t see what’s going on internally, and if it gets marked as a dup you can’t see the progress of the bug it was duped against.</div><div><br class=""></div><div>Fortunately Swift is now open source and has its own more open bug tracker at <a href="http://bugs.swift.org" class="">bugs.swift.org</a>.</div><br class=""><blockquote type="cite" class=""><div style="font-family: Alegreya-Regular; font-size: 15px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" 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?</div></blockquote><br class=""></div><div>Now you’re talking about Xcode, not about Swift itself. Everyone has a love/hate relationship with Xcode (even inside Apple; I used to work there.) It’s a hugely complex app with a thousand competing demands it has to fulfill. Some parts of it suck. Generally they get better over time. The Swift support — and playgrounds in particular — still seem pretty rough. I still spend most of my time with Obj-C and C++, and whenever I do Swift development it feels like I’m using a different, much less stable IDE! I imagine it still needs more time to mature.</div><div><br class=""></div><div>I don’t know if this mailing list is the best place to discuss Xcode issues, even ones related to Swift. Apple has an xcode-users mailing list at <a href="http://lists.apple.com" class="">http://lists.apple.com</a> . It’s a good quality list that I’ve been on for years.</div><br class=""><div class="">—Jens</div></body></html>