> On Oct 7, 2015, at 17:39 , Peter Tomaselli <[email protected]> wrote: > > Genuine question, no snark intended: does your job depend on playgrounds > specifically? Or is it that you’ve found some Swift that crashes SourceKit > and a playground is the easiest way to demonstrate it?
Well, the promise of the playground is fast prototyping. But the problem actually shows up in Xcode, too, since it's a crash in SourceKitService. Just typing away in Xcode makes it crash. If I leave the crash dialog up (i.e. don't click "OK"), I won't get another. But then Xcode puts up a little banner saying it has lost the connection to the SKS, and shifts the code done. After a bit, it re-laucnhes SKS, and removes the banner, shifting the source back up. Repeat ad nauseam. > Slightly OT for this thread I suppose, but if playgrounds have found a > crucial place in anyone’s daily work I’d be interested to hear more about > how, just because that might be fascinating. Playgrounds *could* become an integral part of my workflow, if they didn't constantly get in the way for anything non-trivial. Just like source-level debugging is a requirement these days: you can get away without it, but how productive are you? > FWIW I only use Swift as a hobby at this point and have not had a SourceKit > crash in the Swift 2.0 era, but I have very small toy projects only. > > Perhaps if you post an example of crashy code to the list we can figure out > an alternate construction to keep you moving. Well, I've moved on, unfortunately, and just deleted that code. It's still crashing in Xcode, but less frequently because it's not trying to constantly run it. Soon I won't have to visit that file again for a while. > > Peter > >> On Oct 7, 2015, at 7:04 PM, Rick Mann <[email protected]> wrote: >> >> >>> On Oct 7, 2015, at 15:50 , Kyle Sluder <[email protected]> wrote: >>> >>> On Wed, Oct 7, 2015, at 05:32 PM, Rick Mann wrote: >>>> Is anyone else having this problem, with Swift in general, that >>>> SourceKitService just constantly crashes? Xcode 7.0.1. >>>> >>>> I've reported this bug numerous times, but it's getting to where it's >>>> impossible to get any work done. >>>> >>>> Has anyone found a workaround? >>> >>> It's not useful to think about causes of or workarounds for >> >> On the contrary, I have work to get done. Developing for Apple products is >> not a hobby; it's a multi-billion dollar industry, and I'm a part of it. My >> job depends on it. While not reasonable even in the beta period, crashes >> like this are expected then. But we're at 7.0.1, and these source >> parsing-related crashes are still a common occurrence. >> >> >> >> -- >> Rick Mann >> [email protected] > -- Rick Mann [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
