3 ms·

> I regularly lose syntax coloring. Yep. Happens to me all the time too. Make some changes to code, then wait half a second of the syntax coloring to take ef

• slavapestov 10y ago
  SourceKit itself is fairly stable. However it embeds a copy of the Swift type checker. :-)
  • imron 10y ago
    It's certainly stable, it just likes to take up 100% of the CPU. It happens especially when writing new code or refactoring old code in a medium sized project and using function or variable names that don't yet exist but that I'm about to add in the next few minutes. For example say I want take a chunk of code and move it to a new function fooBar. So I cut the old code and then replace it with a call to a not yet written fooBar function. Then I go to write the definition of fooBar and paste previous code in there but before I can do that, SourceKitService has got itself into a CPU frenzy that won't calm down for 15-20 minutes (even after finishing writing the fooBar function) while it presumably tries to find where fooBar was defined. It's gotten to the point where I have disabled 'live issues' (which seems to exacerbate the problem) and regularly have to kill the SourceKitService process so my fans will go back to normal.