4

When I analyse a Swift project on Xcode 6, the build succeed with no issues. So I wonder if the Clang Static Analyser work with Swift!

Greg Sansom
  • 20,442
  • 6
  • 58
  • 76
Dominique Vial
  • 3,729
  • 2
  • 25
  • 45

1 Answers1

7

As far as I have been able to determine, the static analyser is of no use at all with Swift.

matt
  • 515,959
  • 87
  • 875
  • 1,141
  • 1
    That is why I removed all mention of the Analyser from the latest edition of my books... – matt Jun 08 '15 at 14:53
  • I fervently hope that Apple is going to add support for the static analyzer for Swift in a future update of Xcode. – Duncan C Jun 08 '15 at 15:08
  • @matt, this is annoying as I wanted to use it to find an `EXC_BAD_ACCESS` crash. Have you some tips for such problems? – Dominique Vial Jun 08 '15 at 15:12
  • 1
    That sounds like a different question. Please _ask_ that question (as a question), giving details about the crash, where it occurs, what messages you get, etc., and let's discuss how to track it down. – matt Jun 08 '15 at 15:14
  • Here is the question: http://stackoverflow.com/questions/30683897/runaction-on-sknode-does-not-complete#comment49441652_30683897 – Dominique Vial Jun 08 '15 at 15:16
  • 1
    Would a static analyzer for Swift really be that useful? It seems like the language was designed to prevent a lot of the problems that a static analyzer would catch. – Ferruccio Jun 26 '15 at 15:40
  • @Ferruccio I agree, though, it's not the design of the language, I think, so much as the design of the compiler. Apple is willing to let compilation take longer and have the compiler be "smarter", exploring the _logic_ of your program in ways that were previously the province of the analyser. – matt Jun 26 '15 at 17:02
  • I agree with @Ferruccio; all the logic errors the analyzer used to point seem to be either A) already included in the repertory of compiler warnings, or B) Outright Swift compiler errors. Unless I'm missing something... – Nicolas Miari Nov 13 '15 at 07:25