I posted an error with ubuntu running on <a href="http://swift.org" target="_blank">swift.org</a> and it is currently medium priority and still hasn't been fixed by an "open source" team member and it has been more than two months.<div><br></div><div>Here is the error:</div><div><a href="https://bugs.swift.org/browse/SR-1998">https://bugs.swift.org/browse/SR-1998</a></div><div><br></div><div>Do you really think that is a viable option again?<span></span><br><br>On Tuesday, September 13, 2016, Jens Alfke <<a href="javascript:_e(%7B%7D,'cvml','jens@mooseyard.com');" target="_blank">jens@mooseyard.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><blockquote type="cite"><div>On Sep 13, 2016, at 5:34 PM, Shyamal Chandra via swift-users <<a>swift-users@swift.org</a>> wrote:</div><br><div><div style="font-family:Alegreya-Regular;font-size:15px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">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></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></div><div>Fortunately Swift is now open source and has its own more open bug tracker at <a href="http://bugs.swift.org" target="_blank">bugs.swift.org</a>.</div><br><blockquote type="cite"><div style="font-family:Alegreya-Regular;font-size:15px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">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></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></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" target="_blank">http://lists.apple.com</a> . It’s a good quality list that I’ve been on for years.</div><br><div>—Jens</div></div></blockquote></div>
<br><br>-- <br>Sent from Gmail Mobile<br>